You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the proxy service (and thus the SDK) uses the operation id instead of the path documented in the standard app api to make requests to an app.
So the correspondance would have to be from the operation ids in the specification of the registered app to the paths of the SDK, right? Apps would still indicate the capability in the operation id when they register?
I don't see why not, it should not require much change.
If we want to move forward with this, I would suggest moving it to the GitLab issue board.
Just to make sure we are on the same page, as an example, to list all available transformations, with my proposed change one would make the following call to the proxy:
Currently the proxy service (and thus the SDK) uses the operation id instead of the path documented in the standard app api to make requests to an app.
Example:
python-sdk/marketplace/app/v0/object_storage.py
Line 19 in 5923469
I propose to use the actual paths, not the operation ids, because
However, I'd be interested to hear the arguments for the choice of using the operation ids. @pablo-de-andres @yoavnash Can you comment on this?
The text was updated successfully, but these errors were encountered: