-
Notifications
You must be signed in to change notification settings - Fork 5
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
Structuring APIs #1
Conversation
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 alot of the comments below aren't so much requests for changes, or large issues, but just general considerations about design and intentions.
There's a lot that's left unclear here. The API really needs to be documented somwhere. If it's not in documentation, then atleast in tests. It's hard to follow the intended code flow without some sort of reference as to where data comes in and out from, and what is exposed directly to the user and what is managed by stockroom internally.
As a proof of concept, its good enough for now, but these are just a few things which need consideration before taking this to a "ready for alpha" stage.
306dbac
to
81abb09
Compare
@hhsecond why did you decide not to go with the |
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.
Quite a large PR! This is much more polished, and shows quite a bit of promise for stockroom in the future - in general, nice work!
There are a few issues i've identified which need to be fixed, some which you can use your discression on, and some that are just more for my own understanding.
I haven't tested the code myself yet, so more may follow in the next day or two.
Thanks for the hard work Sherin! looking forward to @lantiga's review!
Codecov Report
@@ Coverage Diff @@
## master #1 +/- ##
=========================================
Coverage ? 90.94%
=========================================
Files ? 15
Lines ? 574
Branches ? 42
=========================================
Hits ? 522
Misses ? 41
Partials ? 11
Continue to review full report at Codecov.
|
5e37be7
to
cae51ad
Compare
This pull request introduces 1 alert when merging a07b749 into 391e143 - view on LGTM.com new alerts:
|
This pull request fixes 4 alerts when merging 4406681 into 391e143 - view on LGTM.com fixed alerts:
|
This pull request fixes 4 alerts when merging 50b5e7c into 391e143 - view on LGTM.com fixed alerts:
|
This pull request fixes 4 alerts when merging 24b6808 into 391e143 - view on LGTM.com fixed alerts:
|
This pull request fixes 4 alerts when merging 2d93209 into 391e143 - view on LGTM.com fixed alerts:
|
This pull request fixes 4 alerts when merging 6a95aa2 into 391e143 - view on LGTM.com fixed alerts:
|
This pull request fixes 4 alerts when merging 87f994b into 391e143 - view on LGTM.com fixed alerts:
|
This pull request fixes 4 alerts when merging 4c3e15e into 391e143 - view on LGTM.com fixed alerts:
|
A massive PR includes the API structuring, test cases, CI setup
What it does not contain
The APIs might need more changes (one I could think off is the have dictionary style access). The primary motive I had while designing the APIs is making user relying on git checkout as much as possible. But I could see why a git + stockroom workflow should be an option but should not be the only workflow possible especially since stockroom allows model storage without user spending time figuring out how to store models. The next release will be a more organized with more API planning analyzing user stories trying out with this release