ref(cells): Remove the includeFeatureFlags query param from the org listing request#115833
Merged
Conversation
…isting call This removes the includeFeatureFlags query param from being sent with the org listing request when linking an organization. - the `features` property is never read anyway - the org listing API won't be able to return features as it's moving to control
github-actions
Bot
added
the
Scope: Frontend
Contributor
📊 Type Coverage Diff✅ No new type safety issues introduced. Coverage: 93.56% |
markstory
reviewed
May 19, 2026
| [getApiUrl('/organizations/'), {query: {include_feature_flags: 1}}], | ||
| {staleTime: Infinity} | ||
| ); | ||
| } = useApiQuery<Organization[]>([getApiUrl('/organizations/')], {staleTime: Infinity}); |
Member
There was a problem hiding this comment.
Should Organization become OrganizationSummary here so that we can use typescript to validate that we aren't using fields that won't be available on the response data?
Member
Author
There was a problem hiding this comment.
Yeah definitely.. though i think gets threaded through into a bunch of places not just here. I'll open a separate PR to update all the types once the dependencies for that are met.
markstory
approved these changes
May 20, 2026
Member
markstory
left a comment
markstory
left a comment
There was a problem hiding this comment.
Looks good to me. The org list data is just used to do counts + make select options so feature flags aren't used.
JonasBa
pushed a commit
that referenced
this pull request
May 21, 2026
…isting request (#115833) This removes the includeFeatureFlags query param from being sent with the org listing request when linking an organization to integration. This change is a no-op: - the `features` property is never read anywhere in the UI code - the org listing API won't be able to return features as it's moving to control
3 tasks
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.
This removes the includeFeatureFlags query param from being sent with the org listing request when linking an organization to integration.
This change is a no-op:
featuresproperty is never read anywhere in the UI code