Add buttons to reorder custom callsign notes #185
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
sd
requested changes
Jan 1, 2026
| disabled={isFirst} | ||
| style={{ marginHorizontal: styles.oneSpace / 2 }} | ||
| > | ||
| {t('general.buttons.moveUp', 'Move Up')} |
Contributor
There was a problem hiding this comment.
Instead of "Up" and "Down", we can better explain what this means by labeling the buttons with something like "Increase priority" and "Decrease priority".
Also, since these labels are rather specific to call notes, I think the translation key should be 'extensions.call-notes.increasePriority' or something like that.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change adds the ability to re-order the custom callsign notes so you can prioritize which note gets pulled if a callsign exists in multiple files.