-
Notifications
You must be signed in to change notification settings - Fork 29
MDG Public API python wrapper #125
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
MDG Public API python wrapper #125
Conversation
|
This pull request has been linked to Clubhouse Story #58204: MDG: Public API. |
FlorentDev64
left a comment
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.
LGTM
FlorentDev64
left a comment
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.
I think that this two routes should be merged into one single route to avoid code duplication.
"GET", "/projects/%s/models/lab/documentations/%s" % (self.mltask.project_key, export_id))
"GET", "/projects/%s/savedmodels/documentations/%s" % (self.saved_model.project_key, export_id))
Because, we do not need to know where the documentation came from (savedModels or 'models/labs). Maybe we should have one single route like "GET", "/projects/%sdocumentations/%s" % (self.saved_model.project_key, export_id))`
If this is done, we should move the route to another file.
@pbailly @adescamps what do you think ? We discussed it and I still think having the route |
Story details : [ch58204]