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

Status.filtered is not null for unfiltered statuses #222

Open
bocops opened this issue Jun 2, 2023 · 0 comments
Open

Status.filtered is not null for unfiltered statuses #222

bocops opened this issue Jun 2, 2023 · 0 comments

Comments

@bocops
Copy link
Collaborator

bocops commented Jun 2, 2023

Documentation states that Status.filtered is optional with the definition

If the current token has an authorized user: The filter and keywords that matched this status.

This is why I implemented this as a nullable value of the Status entity. However, my own use of the filter API seems to suggest that this is actually never not returned with individual statuses. I assumed that I could just test if filtered is non-null to determine that a status is affected by filtering, but this is wrong.

If a status is unaffected by any filters, this will be an empty array "[]" in the returned Json. This can be checked with slight changes to the sample I just provided with #221. I am unsure if we should consider this a bug in Mastodon's documentation, or if we should just add better documentation on our side.

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