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

Clarify handling of optional fields. #4

Open
sirthias opened this issue Mar 9, 2018 · 0 comments
Open

Clarify handling of optional fields. #4

sirthias opened this issue Mar 9, 2018 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@sirthias
Copy link
Contributor

sirthias commented Mar 9, 2018

The Hetzner Cloud API definition defines quite a few request parameters that are optional.
Currently it is unclear how one can define such a parameter as "not set".
Should it be set to null? Are there parameters where the meaning of null differs from not set?

Ideally the fact whether a parameter is optional or not would be expressed through the type system, e.g. via something like Java 8's Optional type.

@sinuscosinustan sinuscosinustan self-assigned this Mar 12, 2018
@sinuscosinustan sinuscosinustan added the help wanted Extra attention is needed label May 11, 2019
@sinuscosinustan sinuscosinustan removed their assignment Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants