You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When modifying a project's settings via the peridot web ui (:////settings), several fields are missing, and when the form is submitted, they are missing from the PUT request to the API causing them to be nulled out.
These fields include cdnURL, streamMode, and buildPoolType.
These settings are modifiable in the API.
I'm not sure if more modern peridot versions have fixed this form.
Reproduction Steps
Have a project
Set a cdnURL (but you can't in the UI, so use the API)
Update the architectures in the /settings page
Note that the cdnURL is missing when looking at the settings again in the API.
Really, this should use PATCH, not PUT to update only the changes. This makes the page more future proof when the data layer changes.
Expected Behavior
The UI should support all the fields available in the Project object. Or it should track the original object and only change the fields present in the form, or it should use PATCH to modify the object state on the server vs. PUT.
Version and Build Information
It is not obvious what version of peridot I'm using, but it's kinda old. IDK if this bug is still relevant.
Additional context
Please close if not relevant to current releases.
The text was updated successfully, but these errors were encountered:
We're not planning to use PATCH as the general pattern is that the resource is replaced wholly. So GET -> PUT is expected. I agree that newer options should have been present in the UI to not cause issues like this.
Describe The Bug
When modifying a project's settings via the peridot web ui (:////settings), several fields are missing, and when the form is submitted, they are missing from the PUT request to the API causing them to be nulled out.
These fields include cdnURL, streamMode, and buildPoolType.
These settings are modifiable in the API.
I'm not sure if more modern peridot versions have fixed this form.
Reproduction Steps
Really, this should use PATCH, not PUT to update only the changes. This makes the page more future proof when the data layer changes.
Expected Behavior
The UI should support all the fields available in the Project object. Or it should track the original object and only change the fields present in the form, or it should use PATCH to modify the object state on the server vs. PUT.
Version and Build Information
It is not obvious what version of peridot I'm using, but it's kinda old. IDK if this bug is still relevant.
Additional context
Please close if not relevant to current releases.
The text was updated successfully, but these errors were encountered: