-
Notifications
You must be signed in to change notification settings - Fork 2
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
Validate objects coming via API in BE via the integrated validator #589
Labels
backend
Backend related task/PR
Comments
tomaspavlin
added
backend
Backend related task/PR
technical debt
nice to have
nice to have things, not urgent for the milestone
and removed
technical debt
labels
Mar 23, 2021
kubantjan
removed
the
nice to have
nice to have things, not urgent for the milestone
label
Jul 11, 2022
kubantjan
changed the title
Validate config and patient parameters in BE
Validate config and patient parameters in BE via the integral validator
Jul 13, 2022
kubantjan
changed the title
Validate config and patient parameters in BE via the integral validator
Validate objects coming via API in BE via the integrated validator
Jul 13, 2022
@kubantjan Is it necessary to create ConfigParametersDTO in CalculateFromConfig endpoint for request_body() or we can just use ConfigParameters? Because creating ConfigParametersDTO would mean code dublication. |
No need :) We would just create it in case there would be some difference needed :) |
krllstdn
pushed a commit
that referenced
this issue
Aug 3, 2022
krllstdn
pushed a commit
that referenced
this issue
Aug 4, 2022
krllstdn
pushed a commit
that referenced
this issue
Aug 5, 2022
krllstdn
pushed a commit
that referenced
this issue
Aug 9, 2022
krllstdn
pushed a commit
that referenced
this issue
Aug 9, 2022
krllstdn
pushed a commit
that referenced
this issue
Aug 9, 2022
krllstdn
pushed a commit
that referenced
this issue
Aug 9, 2022
krllstdn
pushed a commit
that referenced
this issue
Aug 9, 2022
krllstdn
pushed a commit
that referenced
this issue
Aug 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: