Skip to content
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

debt: be more stringent in validating data sent to soilDataPush mutation #1526

Open
shrouxm opened this issue Oct 31, 2024 · 0 comments
Open

Comments

@shrouxm
Copy link
Member

shrouxm commented Oct 31, 2024

Currently if the user sends duplicate entries to the soilDataPush mutation we just apply the entries. Ideally clients should only specify entities once, to make intent unambiguous, and not doing so could be a smell that there's a client bug on the loose, so we should reject such requests. As it stands that could mean:

  • sending duplicate sites
  • sending duplicate depth dependent data entries
  • sending duplicate depth intervals for update or deletion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

1 participant