🐛 Resolve string variables in route paths#66
Merged
savannahostrowski merged 2 commits intomainfrom Feb 17, 2026
Merged
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.
Closes #49
This was a good catch. The fix here is to extract string variables to build up a map and then replace matching variable names with extracted paths. This will work for most cases. There is an edge case that I would like to defer, since I think it's pretty uncommon and requires a bunch more complexity:
This obviously won't work but our resolution logic will incorrectly replace it.
I've also fixed the tooltip to strip unresolvable dynamic prefixes (like
settings.API_PREFIX) instead of showing them as if they were path parameters