Repository navigation
chore(api): expose attribute context in endpoint - #127372
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 1add095. Configure here.
|
If we're now showing in public docs, can we mark it as "experimental" in the description like we do other apis that are still in development? |
|
Turning back to draft and checking if we can just update CLI directly to expose the context |
| exclude=True, | ||
| # The endpoint is PUBLIC, but the context shape is still evolving, so only this | ||
| # parameter is flagged experimental. | ||
| extensions={"x-sentry-experimental": True}, |
There was a problem hiding this comment.
Not sure if is this extensions part is needed, but I can remove it and the unit test if it suffices to just update the description
There was a problem hiding this comment.
I don't think this is doing anything today, but we probably should use it so worth adding still
wmak
left a comment
There was a problem hiding this comment.
lgtm, I might follow up with a change to make marking parameters as experimental cleaner
| exclude=True, | ||
| # The endpoint is PUBLIC, but the context shape is still evolving, so only this | ||
| # parameter is flagged experimental. | ||
| extensions={"x-sentry-experimental": True}, |
There was a problem hiding this comment.
I don't think this is doing anything today, but we probably should use it so worth adding still

Changes
Addresses EXP-1293 by letting context be exposed so CLI can access it