#678 Mastodon 4.6.0: Update accounts API#709
Draft
PattaFeuFeu wants to merge 12 commits into
Draft
Conversation
PattaFeuFeu
force-pushed
the
improvement/#678/update-accounts
branch
from
June 14, 2026 12:55
9af713c to
6e82aa1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Relates to: #678
Note
Based on #708, so merge that one first. I’ll keep this one here a draft until then.
Type of Change
Breaking Changes
ProfileFieldsextractionProfileFieldsmoved from being a subclass ofAccountMethodsto being its own class in thesocial.bigbone.Parameterspackage.Imports change to:
ProfileFields“rules”Character count
Previously, we hardcoded a max character count for both
ProfileFieldNameandProfileFieldValue. With Mastodon 4.6.0, 255 characters are only the default that may be overridden by an instance. We have removed the hardcoded character limit and ask callers to checkInstanceproperties first.Fields count
Same with the amount of fields. Previously, a maximum of four profile fields was enforced. With Mastodon 4.6.0, that count is officially configurable, but still defaulting to
4. To account for that,ProfileFieldschange from adata classwith 4 values to avalue classwhich wraps aMap<ProfileFieldName, ProfileFieldValue>which may contain any amount of fields. Again, callers are asked to checkInstanceproperties first to ensure correct max count matching the instance.How Has This Been Tested?
Mandatory Checklist
gradle checkand there were no errors reportedOptional checks
*Methodsclasses: Did you also reference it in theMastodonClientmain class?/docsfolder (e.g. API Coverage page)?