-
Notifications
You must be signed in to change notification settings - Fork 41
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
minor: Connection.create_job vs DataCube.send_job #276
Comments
fwiw, that's also how it's called in all other clients, I think. |
soxofaan
added a commit
that referenced
this issue
Mar 14, 2022
Is more consistent internally and compared to other libraries/documentation
soxofaan
added a commit
that referenced
this issue
Mar 14, 2022
Is more consistent internally and compared to other libraries/documentation
soxofaan
added a commit
that referenced
this issue
Mar 15, 2022
Is more consistent internally and compared to other libraries/documentation
soxofaan
added a commit
that referenced
this issue
Mar 15, 2022
soxofaan
added a commit
that referenced
this issue
Mar 16, 2022
…_job` Is more consistent internally and compared to other libraries/documentation
soxofaan
added a commit
that referenced
this issue
Mar 17, 2022
…_job` Is more consistent internally and compared to other libraries/documentation
done |
soxofaan
added a commit
to openEOPlatform/documentation
that referenced
this issue
May 10, 2022
soxofaan
added a commit
to openEOPlatform/documentation
that referenced
this issue
May 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Connection.create_job
vsDataCube.send_job
having differently named methods for same thing in different context is bit confusing when depending on code completion feature.
Let's settle on
create_job
(because that is also the verb used in openEO api)?The text was updated successfully, but these errors were encountered: