Skip to content
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

Clarification on PUT /process_graphs #449

Closed
Ardweaden opened this issue May 17, 2022 · 1 comment
Closed

Clarification on PUT /process_graphs #449

Ardweaden opened this issue May 17, 2022 · 1 comment
Assignees
Milestone

Comments

@Ardweaden
Copy link
Collaborator

Ardweaden commented May 17, 2022

https://docs.openeo.cloud/api/#tag/User-Defined-Processes/operation/store-custom-process

Documentation states:

The id MUST be unique for the authenticated user, including all pre-defined processes by the back-end.

id: The identifier for the process. It MUST be unique across its namespace (e.g. pre-defined processes or user-defined processes).

I assume the second one is correct? I see there are some new proposals that will handle it that way.

Additionally

Clients SHOULD warn the user if a user-defined process is added with the same identifier as one of the pre-defined process.

Not sure why this is stated here, but the back-end does not need to warn, correct?

Thanks for help.

@m-mohr
Copy link
Member

m-mohr commented May 17, 2022

Yes, it's the latter, but as a back-end I'd still implement to check whether a user process would conflict with a pre-defined process just to avoid confusion.

The note for clients is there because the API docs are for clients and back-ends. :-) As such, there are also some guidelines specifically for clients. Back-ends don't need to warn (but I'd personally reject them as mentioned above).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants