Improve data logger validation error messages #4603
Draft
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.
Any background context you want to provide?
The data logger create/update modal had some hard coded error messages and backend logic that didn't align.
What's this PR do?
Dynamically displays error messages to the user
Refactors the create and update endpoints to use a serializer to validate data and generate errors.
Based on the existing data logger model, the only required fields are property, display_name, and is_occupied_data. I used this as the source of truth for refactoring the view logic.
How should this be manually tested?
Create/update a data logger, make sure error messages are applicable.
What are the relevant tickets?
#4592
Screenshots (if appropriate)