HTTP migration writese plugin properties on comment. #223
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.
This pull request introduces enhancements to the JSDoc comment generation logic in
HttpMigrateRouteComposer, making the generated documentation more comprehensive and extensible, especially for plugin properties. It also adds a new test to verify the correct inclusion and formatting of custom plugin fields in the route comments.Enhancements to JSDoc comment generation:
HttpMigrateRouteComposerto include additional sections such as security, tags, deprecation status, and custom plugin properties (fields starting withx-). This ensures that any relevant OpenAPI extensions are now documented in the generated comments. [1] [2] [3]Testing improvements:
test_http_migrate_route_plugin, to verify that custom plugin fields (e.g.,x-autobe-specification) are correctly included in the generated route comments and formatted as expected.Package version update:
package.jsonfrom6.0.0to6.0.1to reflect the new features and improvements.