feat: added-query-param-to-get-segment-feature-states

[Zaimwa9]

Thanks for submitting a PR! Please check the boxes below:

• I have added information to docs/ if required so people know about the feature!
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?
• I have used a Conventional Commit title for this Pull Request

Changes

• GET /api/v1/projects/{project_id}/features/?environment={env_id}&segment={segment_id}endpoint now accept query-string params?segment=xx` to return the requested segment' feature states

Added segment_feature_state to response when segment=xx is passed in. Without or with invalid segment, the response is untouched

From V1 to V2:
Frontend was initially going to get the features list and reconciliate the feature states with it. However we realized that this could lead to some loopholes due to features list pagination.
V2 includes a new query param in order to attach the segment_feature_state to the features list to avoid pagination discrepancies.

How did you test this code?

• Added tests
• Ran query

Example payload:

{
            "id": 21,
             ....
            "uuid": "1a56cd3c-611a-407f-9dd3-13a10580c7ca",
            "project": 3,
            "environment_feature_state": {
                "id": 565,
                "feature_state_value": null,
                "environment": 8,
                "identity": null,
                "feature_segment": null,
                "enabled": false
            },
            "segment_feature_state": null,
            "num_segment_overrides": 0,
             ....
            "metadata": [],
            "code_references_counts": []
        },

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ignored	Preview		Oct 28, 2025 2:07pm
flagsmith-frontend-preview	Ignored	Preview		Oct 28, 2025 2:07pm
flagsmith-frontend-staging	Ignored	Preview		Oct 28, 2025 2:07pm

[github-actions]

Docker builds report

Image	Build Status	Security report
ghcr.io/flagsmith/flagsmith-api-test:pr-6156	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-api:pr-6156	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith:pr-6156	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-private-cloud:pr-6156	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-frontend:pr-6156	Finished ✅	Results ✅

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.01%. Comparing base (6905e70) to head (ff9dc4e).
⚠️ Report is 19 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6156   +/-   ##
=======================================
  Coverage   98.00%   98.01%           
=======================================
  Files        1278     1278           
  Lines       45122    45178   +56     
=======================================
+ Hits        44223    44280   +57     
+ Misses        899      898    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Zaimwa9]

Couple of changes @gagantrivedi 🙏 :
From V1 to V2:
Frontend was initially going to get the features list and reconciliate the feature states with it. However we realized that this could lead to some loopholes due to features list pagination.
V2 includes a new query param in order to attach the segment_feature_state to the features list to avoid pagination discrepancies.

[kyle-ssg]

This simplifies the FE so much! Tested with the code in #6137