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.

Sign up for GitHub

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

Jump to bottom

Object create without endAt: suspected bug in API spec #349

Open
sergei-maertens opened this issue Sep 27, 2023 · 0 comments
Open

Object create without endAt: suspected bug in API spec #349

sergei-maertens opened this issue Sep 27, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@sergei-maertens
Copy link
Member

sergei-maertens commented Sep 27, 2023 •
edited
Loading

Version: latest / 2.1 (API spec)

When I create an object with unknown end date, then this is typically stored as null in the database. Then I also expect to receive null in the response JSON (record.endAt: null). However, the API spec documents this as string(date) and does not show it could be null too:

image

This is all theory and untested - possibly the API returns an empty string for empty values.
@sergei-maertens sergei-maertens added the bug Something isn't working label Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sergei-maertens