-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add management and performance URL schemes #237
Conversation
Renamed icarErrorResource to icarBatchResultMessage, and added icarBatchResultSeverityType enum.
Batch POSTS now always return an array of icarBatchResult, each of which may contain an array of icarErrorWarningMessageResource. Single POSTs if successful return the posted object (ID filled in), otherwise they return an errors array of icarErrorWarningMessageResource. Sorry for renaming the file, but it helped to clarify its purpose.
Renamed icarErrorWarningMessage Resource to icarResponseMessageResource based on feedback to PR adewg#232
Added URL schemes for management (animal sets, animal set join/leave, and devices), and performance (weights, conformation scores, breeding values). Along with other commits, resolves adewg#154.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added comments regarding batch urls. Should we use "locations" sub-path as for get/single post endpoints?
As I see this PR also includes the changes from previous POST PRs. To by completing this one we'll resolve all the rest :)
} | ||
} | ||
}, | ||
"/batches/{location-scheme}/{location-id}/diagnoses": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should "locations" path be added after /batches -> "/batches/locations/{location-scheme}/{location-id}/diagnoses"? This question also applies to all the other "batches" endpoints.
url-schemes/managementURLScheme.json
Outdated
} | ||
} | ||
}, | ||
"/batches/{location-scheme}/{location-id}/animal-sets": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should "locations" path be added after /batches -> "/batches/locations/{location-scheme}/{location-id}/diagnoses"? This question also applies to all the other "batches" endpoints in managementURLScheme.json.
} | ||
} | ||
}, | ||
"/batches/{location-scheme}/{location-id}/weights": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should "locations" path be added after /batches -> "/batches/locations/{location-scheme}/{location-id}/diagnoses"? This question also applies to all the other "batches" endpoints in performanceURLScheme.json.
Based on comments in the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok for me, no remarks
Added URL schemes for management (animal sets, animal set join/leave, and devices), and performance (weights, conformation scores, breeding values).
Along with other PRs, resolves #154.