Fix context inclusion issues #8302
Merged
Conversation
This file contains 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
psiinon
approved these changes
Jan 15, 2024
ricekot
changed the title
When a strict regex was used (e.g. when import OpenAPI specs), there were issues with including or excluding endpoints from the context because of improper parsing of nodeNames of: * Endpoints with path params (Data Driven Nodes) * Endpoints with both query and form params Signed-off-by: ricekot <github@ricekot.com>
kingthorin
approved these changes
Jan 20, 2024
|
I'm assuming @thc202 will want to review this as well. |
|
Yes. |
|
Thank you! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When a strict regex was used (e.g. when importing OpenAPI specs), there were issues with including or excluding endpoints from the context because of improper parsing of nodeNames. This included: