Add API to manually update database before writing files #55
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
My Python package doesn't work well with static analysis since I'm setting
__all__programmatically at runtime. I also have docstrings which are dynamically modified upon import, avoiding a lot of maintenance.I found this project to be a great fit otherwise, and a nice improvement over AutoAPI. I was able to handle my use case by adding a simple callback which is invoked after the database is built, but before files are generated. In this callback I can fix
all, update docstrings, etc.Thanks for considering! I'd be happy to cleanup / add tests if this change is acceptable.