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

FilterResult.status_matches is a List<String>? #3634

Merged
merged 2 commits into from
May 9, 2023
Merged

FilterResult.status_matches is a List<String>? #3634

merged 2 commits into from
May 9, 2023

Conversation

nikclayton
Copy link
Contributor

@nikclayton nikclayton commented May 8, 2023

This was a Mastodon documentation bug, and is being fixed on their side in mastodon/mastodon#24900.

it is unclear what the correct type should be.

The Mastodon documentation is inconsistent, it's either a `String?`, or a `List<String>?`.

Getting this wrong crashes during JSON parsing.

Since the field isn't used anywhere in Tusky yet it's easier to comment this out so it is not deserialized.

This can be restored when mastodon/mastodon#24900 is fixed.
@nikclayton nikclayton requested review from Tak and connyduck May 8, 2023 11:54
@nikclayton nikclayton changed the title Comment out FilterResult.status_matches FilterResult.status_matches is a List<String>? May 8, 2023
@nikclayton nikclayton requested review from Tak and connyduck May 8, 2023 19:43
@nikclayton
Copy link
Contributor Author

They're updating the docs and confirmed it's List<String>?, so I've updated this to match.

@nikclayton nikclayton merged commit b12e772 into tuskyapp:develop May 9, 2023
@nikclayton nikclayton deleted the 3551-remove-status_matches branch May 9, 2023 15:56
@connyduck
Copy link
Collaborator

I'd still argue for commenting it out, deserializing something that is not used is a waste of resources.

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

Successfully merging this pull request may close these issues.

3 participants