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
Describe the bug
The metadata service is returning the message Valid Model even for models that are expected to have validation errors (for ex when required fields are missing). Issue caught by @saskiad
To Reproduce
service returns "valid model" when required fields are missing
eg. http://aind-metadata-service/procedures/653980
This says the model is valid but there is no injection_volume field, which is a required field. Expected behavior
should catch the validation errors for each of the procedure models and include that in message.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
The metadata service is returning the message Valid Model even for models that are expected to have validation errors (for ex when required fields are missing). Issue caught by @saskiad
To Reproduce
service returns "valid model" when required fields are missing
eg. http://aind-metadata-service/procedures/653980
This says the model is valid but there is no injection_volume field, which is a required field.
Expected behavior
should catch the validation errors for each of the procedure models and include that in message.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: