Repository navigation
docs(app): document repeater nicknames - #40
Merged
Merged
Conversation
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
1 participant
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.
Summary
Documents the app's new repeater nicknames (MeshMapper/MeshMapper_Flutter_App#36, for MeshMapper/MeshMapper_Project#557).
Repeater Nicknamesentry covering what it does, the 8-character limit, where nicknames show, the one-repeater rule, how to add, edit and remove one, and that nicknames stay on the phone across regions.Merge after the app PR ships, since it describes app behaviour.
Testing
mkdocs build --strictpasses (built in a scratch venv), and the new#repeater-nicknamesanchor resolves.