-
Notifications
You must be signed in to change notification settings - Fork 415
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: Limit segment rules and conditions #3397
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Uffizzi Preview |
Co-authored-by: Matthew Elwell <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3397 +/- ##
==========================================
+ Coverage 95.91% 95.93% +0.01%
==========================================
Files 1085 1087 +2
Lines 33677 33805 +128
==========================================
+ Hits 32302 32430 +128
Misses 1375 1375 ☔ View full report in Codecov by Sentry. |
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.
Added a couple of comments to the code. I think we should also document this in the system limits section of the docs.
Have we confirmed yet how the FE behaves in this case too?
The mishandled errors have been fixed in this PR: #3413 |
Ok no problem. Added this locally. |
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingI have added information todocs/
if required so people know about the feature!Changes
Introduce a limit via settings constant to limit the number of conditions a segment can undergo before rejection.
How did you test this code?
Two long unit tests one for the update the other for the create. Existing tests can handle the cases where we want to see segments created in response to API input.