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

API documentation: Inconsistent date/time format for Account #26843

Closed
illdefined opened this issue Sep 7, 2023 · 0 comments · Fixed by mastodon/documentation#1322
Closed
Labels
bug Something isn't working status/to triage This issue needs to be triaged

Comments

@illdefined
Copy link

Steps to reproduce the problem

The client API documentation for Account gives the type for the last_status_at field as nullable ISO 8601 date (see https://docs.joinmastodon.org/entities/Account/#last_status_at) and appears to be what the server implements.

The example provided however gives last_status_at as ISO 8601 date/time with decimal fraction and timezone: https://docs.joinmastodon.org/entities/Account/#example.

Expected behaviour

The date formats should be consistent between field documentation and example.

Actual behaviour

The date formats are inconsistent.

Detailed description

No response

Mastodon instance

No response

Mastodon version

No response

Technical details

No response

@illdefined illdefined added bug Something isn't working status/to triage This issue needs to be triaged labels Sep 7, 2023
untitaker added a commit to untitaker/documentation that referenced this issue Oct 12, 2023
this api returns just the date, no time component

fix mastodon/mastodon#26843
ClearlyClaire pushed a commit to mastodon/documentation that referenced this issue Oct 13, 2023
this api returns just the date, no time component

fix mastodon/mastodon#26843
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working status/to triage This issue needs to be triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant