-
Notifications
You must be signed in to change notification settings - Fork 9
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
Compatibility with upcoming version of scicat backend #18
Comments
Several issues that we might want to take care of at the same time. There is enough different between the new nest.js backend and the old one that right now, pyscicat will not work with the new version. The major different is that the endpoints have changed. The issues I know about today are that there used to be three sets of we need to decide how to deal with it. At this point, the new version has one set of dataset endpoints, while the old version has three: The version of the api that pyscicat talks to is sent with the URL that the called uses to construct the pyscicat instance. I propose making changes to pyscicat with the following goals in mind:
To do this, I propose:
Adding to this conversaion @nitrosx @abigailalexander |
At the developer's meeting, we discussed the future of the version indicator in the URL. It was decided that we would leave it as We also discussed the impact of making breaking changes to pyscicat at this point. We would like to simplify a little, removing the multiple calls to data set types. So we propose to remove the |
The upcoming backend has different endpoints than the production (loopback) version of backend. Several things known:
-(Edit, this is not the case)v3
is nowv4
Raw
andDerived
The text was updated successfully, but these errors were encountered: