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

rename ViewerAction.EDIT_NOTE #17661

Merged
merged 1 commit into from
Dec 26, 2024
Merged

rename ViewerAction.EDIT_NOTE #17661

merged 1 commit into from
Dec 26, 2024

Conversation

BrayanDSO
Copy link
Member

to EDIT

this allows to share the same preference key of ViewerCommand, since the name is the same now

This change will reset its position in the toolbar, but it doesn't need a preference upgrade because the new reviewer is a developer option

Checklist

Please, go through these checks before submitting the PR.

  • You have a descriptive commit message with a short title (first line, max 50 chars).
  • You have commented your code, particularly in hard-to-understand areas
  • You have performed a self-review of your own code
  • UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
  • UI Changes: You have tested your change using the Google Accessibility Scanner

to EDIT

this allows to share the same preference key of `ViewerCommand`, since the name is the same now

This change will reset its position in the toolbar, but it doesn't need a preference upgrade because the new reviewer is a developer option
Copy link
Member

@david-allison david-allison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should have a test which breaks on changes which would invalidate preferences. Fine to do in alpha. We should do this with intent in production.

In general: it's 'edit card' if coming from the reviewer: might not be when we move to the new editor, but for now we can display the correct deck/card template if a card is provided

@david-allison david-allison added the Needs Second Approval Has one approval, one more approval to merge label Dec 25, 2024
@BrayanDSO
Copy link
Member Author

We should have a test which breaks on changes which would invalidate preferences.

Gonna do some when the new reviewer is promoted to an Advanced > Experimental setting. Not now to avoid spending time fixing emerging changes like this one

@david-allison
Copy link
Member

Sounds good to me

Copy link
Member

@mikehardy mikehardy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM as well as all related discussion about testing, and not needed in alpha etc +1

@mikehardy mikehardy added this pull request to the merge queue Dec 26, 2024
Merged via the queue into ankidroid:main with commit 9179fd2 Dec 26, 2024
12 checks passed
@github-actions github-actions bot removed the Needs Second Approval Has one approval, one more approval to merge label Dec 26, 2024
@github-actions github-actions bot added this to the 2.21 release milestone Dec 26, 2024
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