Repository navigation
fix(health): recognize FastAPI guard-named dependencies (#7) - #39
Merged
haydenschmitty merged 1 commit intoNov 2, 2026
Merged
Conversation
7 tasks done
Owner
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.
Addresses the first FastAPI pattern of #7. Extend the guard-name heuristic to recognize a guard segment in dependencies such as metrics_guard. Added a regression fixture with a protected billing route and a public logger-only control route. The test failed before and passed after the fix; npm test passed (163 passing, 1 skipped).