-
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: Validate feature values before saving #4043
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Uffizzi Preview |
Hmm... @kyle-ssg it looks like it's not clearing the state after failing validation once, see here: https://www.loom.com/share/37b89881d8f34b32a99d6e1101cb3bf0?sid=088017f1-ba32-40e3-9c70-ec6f67637e73 |
@kyle-ssg I've found one more way to get around the validation, which is by editing a segment override from the segment definition itself: Screen.Recording.2024-05-29.at.13.18.11.movEverything else I've tested works well 👍 |
@rolodato good spot, associated segment overrides will now include this too |
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingdocs/
if required so people know about the feature!Changes
Fixes the icon for when language validation fails

Saving features, segment overrides and creating change requests will now validate values in the same way.

How did you test this code?
Attempted to create an invalid change request, segment override and remote config