Fix URL Path Handling Issues in Django and Spring Analyzers #450
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
…point extraction ref: #428 Signed-off-by: ksg <[email protected]>
ref: #428 Signed-off-by: ksg <[email protected]>
ksg97031
force-pushed
the
fix/django-spring-url-handling
branch
from
40d1924 to
14c63fb
Compare
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.
This PR addresses two issues in the URL handling logic within Django and Spring analyzers.
Fixes
@visited_url_pathsto track and avoid duplicate processing of URL paths, optimizing endpoint extraction.class_annotation.params[0]to prevent potential out-of-bounds errors during URL extraction.Testing
The updates were tested to ensure accurate endpoint extraction and to prevent any unintended behavior changes.