Skip to content

bug(nimbus): set default values on backend, not frontend#13116

Merged
jaredlockhart merged 3 commits intomainfrom
13113
Jul 29, 2025
Merged

bug(nimbus): set default values on backend, not frontend#13116
jaredlockhart merged 3 commits intomainfrom
13113

Conversation

@jaredlockhart
Copy link
Collaborator

Because

  • We recently added a case that prepopulate the feature value with "{}" when features are selected
  • This caused the frontend to display "{}" as the feature value, and yet in the backend it is None
  • This causes the review serializer to indicate that a field is not filled in when it looks as if it is

This commit

  • Removes the default "{}" value from the frontend
  • Sets it in the backend
  • This way the state displayed and state validated are the same

fixes #13113

Copy link
Contributor

@yashikakhurana yashikakhurana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perfect, quick fix, thank you @jaredlockhart

Because

* We recently added a case that prepopulate the feature value with "{}" when features are selected
* This caused the frontend to display "{}" as the feature value, and yet in the backend it is None
* This causes the review serializer to indicate that a field is not filled in when it looks as if it is

This commit

* Removes the default "{}" value from the frontend
* Sets it in the backend
* This way the state displayed and state validated are the same

fixes #13113
@jaredlockhart jaredlockhart added this pull request to the merge queue Jul 29, 2025
Merged via the queue into main with commit 20822af Jul 29, 2025
15 checks passed
@jaredlockhart jaredlockhart deleted the 13113 branch July 29, 2025 01:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Empty feature values should be valid

3 participants