Fix Sound Event Geometry Update Bug #45
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When annotating, updating a sound event's geometry caused it to visually revert to its original state. This was due to a type mismatch between
soundevent.data.Feature (returned by the update function) and the expected whombat.schemas.Feature in the client's validation layer. The difference stems from the recent addition of terms to soundevent.
This PR resolves the issue by correctly casting soundevent.data.Feature to whombat.schemas.Feature before sending the data back to the client. This ensures the validation passes and the updated geometry persists.