-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(versioning): handle versioned environments for associated-features endpoint #4735
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Docker builds report
|
Uffizzi Preview |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4735 +/- ##
=======================================
Coverage 97.21% 97.22%
=======================================
Files 1172 1172
Lines 40535 40569 +34
=======================================
+ Hits 39408 39443 +35
+ Misses 1127 1126 -1 ☔ View full report in Codecov by Sentry. |
4366e68
to
8a077c1
Compare
# Conflicts: # frontend/web/components/modals/AssociatedSegmentOverrides.js
@@ -593,6 +593,10 @@ class Meta: | |||
fields = ("id", "feature", "environment") | |||
|
|||
|
|||
class AssociatedFeaturesQuerySerializer(serializers.Serializer): | |||
environment = serializers.IntegerField(required=False) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a note to self — we do seem to have a convention to use entity
, not entity_id
, for query filters. The rule is only broken for the evaluation-data
endpoint, which has an environment_id
filter.
Changes
Adds a new query parameter to the
segments/:id/associated-features/
endpoint which allows us to filter segment overrides by the current environment, and hence we can filter by latest versions.How did you test this code?
Added unit test for the API.
Tested FE changes locally.