-
Notifications
You must be signed in to change notification settings - Fork 234
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
Move API clients into separate packages #3124
Conversation
f20e882
to
c2e2470
Compare
{ | ||
"name": "genome-nexus-ts-api-client", | ||
"description": "Genome Nexus API Client for TypeScript", | ||
"version": "0.1.0", |
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.
This version should reflect the actual API version, ideally the latest tag version on genome-nexus master branch.
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.
setting this to 1.1.2-beta.0
for now. latest master is 17 commits ahead of the latest release 1.1.1
so it is better set it to the next beta version.
{ | ||
"name": "oncokb-ts-api-client", | ||
"description": "OncoKB API Client for TypeScript", | ||
"version": "0.1.0", |
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.
This version should reflect the actual API version, ideally the latest tag version on oncokb master branch
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.
e9b69fa
to
0123ec6
Compare
@@ -1,6 +1,7 @@ | |||
{ | |||
"name": "cbioportal-frontend", | |||
"private": true, | |||
"version": "3.2.13-alpha.0", |
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 version back to make updatePackageVersion
also update the root package.json
dependencies. If the version is missing, lerna ignores this file completely when updating other package versions.
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.
when do we need to update this? In every 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.
It is not critical to update this version every time. The main reason to have a version in this package.json
is to make lerna version
to properly update dependencies. It would be nice to keep this version in sync with the tagged master version though.
@@ -336,8 +336,6 @@ then update all package versions with: | |||
yarn run updatePackageVersion | |||
``` | |||
|
|||
After that update the versions of all packages in the root `package.json` |
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.
We don't need to do this anymore, instead we are adding version
back to the root package.json
and let lerna version
handle dependencies automatically like it does with all other versioned packages.
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.
Finally! Nice work! Thanks。
@onursumer potentially, I guess most times you would want to use the API + components. But maybe it's useful to allow API access as well without using mobx + components. If it's not extra maintenance effort then why not I guess |
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.
Nice! 🎉
Just one question re: when to update the root package version. For the other clients it's obvious I think, whenever the API updates we should update the client and all packages depending on that client. But for the root package it's not that obvious when we update that number? Whenever we tag a release or something?
@inodb ideally root We can even remove the version from the root |
ad5ab19
to
c730f6b
Compare
@@ -131,7 +132,8 @@ | |||
"bootstrap-sass": "3.3.7", | |||
"bowser": "^1.7.1", | |||
"bundle-loader": "^0.5.4", | |||
"cbioportal-frontend-commons": "0.2.6", | |||
"cbioportal-frontend-commons": "^0.2.7", | |||
"cbioportal-ts-api-client": "^1.0.0-beta.0", |
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.
Current API version in swagger doc is 1.0 (beta)
1066c6e
to
ecdfd02
Compare
Signed-off-by: Onur Sumer <s.onur.sumer@gmail.com>
Signed-off-by: Onur Sumer <s.onur.sumer@gmail.com>
Signed-off-by: Onur Sumer <s.onur.sumer@gmail.com>
ecdfd02
to
9bf8a68
Compare
Move API clients into separate packages Former-commit-id: 265dfcc
Separated out OncoKB and Genome Nexus API clients into their own packages. Now we can publish these API clients as standalone packages.
Checks