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

Find a good way to work with optional fields #28

Open
haraldmeyer opened this issue Sep 18, 2024 · 0 comments
Open

Find a good way to work with optional fields #28

haraldmeyer opened this issue Sep 18, 2024 · 0 comments

Comments

@haraldmeyer
Copy link

As most / all fields are optional the the JSON schema of the OpenAPI specification they are all marked as optional. This makes it difficult to work with the fields.

Challenge is that some fields are known to always be present in responses from C8Y (like ID in most objects and the severity in alarms) but some other fields MUST be empty on POST requests (like ID).

Maybe there is a good way of supporting both cases?

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

No branches or pull requests

1 participant