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

Better wording about case insensitive handling #371

Closed
soxofaan opened this issue Apr 7, 2021 · 3 comments · Fixed by #372
Closed

Better wording about case insensitive handling #371

soxofaan opened this issue Apr 7, 2021 · 3 comments · Fixed by #372
Milestone

Comments

@soxofaan
Copy link
Member

soxofaan commented Apr 7, 2021

(from Open-EO/openeo-processes-python#22)

Format names are allowed to be *case insensitive* throughout the API.

Wording is bit confusing (sound like backend can choose to be case insensitive or not).

Proposal:

Format names MUST be handled case insensitively throughout the API.

Same applies to Service names and Billing plans

@m-mohr
Copy link
Member

m-mohr commented Apr 7, 2021

Just made a change, but my git is acting up and I can't commit yet. Will be available "soon".

@m-mohr
Copy link
Member

m-mohr commented Apr 7, 2021

it is:

Format names MUST be accepted case insensitive throughout the API.

m-mohr added a commit that referenced this issue Apr 7, 2021
@m-mohr m-mohr linked a pull request Apr 7, 2021 that will close this issue
@m-mohr
Copy link
Member

m-mohr commented Apr 7, 2021

See PR #372

m-mohr added a commit that referenced this issue Apr 7, 2021
* Clarified that billing plans, service names and file formats must be accepted case-insensitive. #371
@m-mohr m-mohr added this to the 1.1.0 milestone Apr 7, 2021
@m-mohr m-mohr closed this as completed Apr 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants