Mention accessed property key path in perception warnings#167
Merged
stephencelis merged 7 commits intopointfreeco:mainfrom Oct 23, 2025
Merged
Mention accessed property key path in perception warnings#167stephencelis merged 7 commits intopointfreeco:mainfrom
stephencelis merged 7 commits intopointfreeco:mainfrom
Conversation
pyrtsa
changed the title
stephencelis
approved these changes
Oct 23, 2025
Member
|
Thanks! |
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
2 participants
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.
Improvement suggestion. I think including the accessed property key path in perception warnings would improve developer experience, even if you can usually find it by expanding the call stack in runtime warnings.
Built as one commit on top of #166 which fixes the unit tests.