Conversation
We've been putting some features behind long lived flags (eg. stats) to help double check outcomes while not showing them to users as they are confusing and unrelated to their billing. Instead of multiple flags, for long lived explore dev features, this flag can be used moving forward.
github-actions
Bot
added
the
Scope: Backend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
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.
Reviewed by Cursor Bugbot for commit f5ff9ee. Configure here.
| # Enable the expand/collapse table height toggle in the logs UI | ||
| manager.add("organizations:ourlogs-table-expando", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=True) | ||
| # Enable various explore related dev features, may be used by internal branches for testing. | ||
| manager.add("organizations:explore-dev-features", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=True) |
There was a problem hiding this comment.
Feature flag placed in wrong alphabetical position
Low Severity
The explore-dev-features flag is added at line 504 (between the ourlogs and tracemetrics sections), but the file's convention (stated on line 30) requires alphabetical ordering. The existing explore-errors flag is at line 126, and explore-dev-features alphabetically precedes it, so the new flag belongs near line 125–126 alongside the other explore-* flags.
Reviewed by Cursor Bugbot for commit f5ff9ee. Configure here.
2 participants
Summary
We've been putting some features behind long lived flags (eg. stats) to help double check outcomes while not showing them to users as they are confusing and unrelated to their billing. Instead of multiple flags, for long lived explore dev features, this flag can be used moving forward.