Add opt-in support for automatically annotating routes after migration tasks #293
+63
−15
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
…n tasks This change introduces an opt-in feature that allows users to automatically annotate routes after running migration tasks. A new method, `Runner.run_after_migration`, has been added for this purpose, and the `annotate_models_migrate.rake` task has been updated to call this new method instead of invoking `Runner.run(["models"])` directly. The `auto_annotate_routes_after_migrate` option has been added to the `Options` class, enabling users to turn this behavior on by specifying `auto_annotate_routes_after_migrate: true` in their `.annotaterb.yml`. Corresponding tests have also been added. Refs: drwl#251
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Thank you as always for maintaining this project. I really appreciate your continued work.
This change introduces an opt-in feature that allows users to automatically annotate routes after running migration tasks. A new method,
Runner.run_after_migration, has been added for this purpose, and theannotate_models_migrate.raketask has been updated to call this new method instead of invokingRunner.run(["models"])directly.The
auto_annotate_routes_after_migrateoption has been added to theOptionsclass, enabling users to turn this behavior on by specifyingauto_annotate_routes_after_migrate: truein their.annotaterb.yml. Corresponding tests have also been added.Refs: #251