feat(fields): allow insertion of 'special fields' with preview #20041
+1,129
−63
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
I will be extending this class to handle field filters and special fields * rendering the output is now the responsibility of `renderToTemplateTag()` rather than done in the CardTemplateEditor
Contributor
|
Important Maintainers: This PR contains Strings changes
|
david-allison
commented
Jan 7, 2026
| val dialog = | ||
| AlertDialog.Builder(requireContext()).create { | ||
| title(R.string.card_template_editor_select_field) | ||
| negativeButton(R.string.dialog_cancel) |
david-allison
force-pushed
the
better-add-field
branch
2 times, most recently
from
3a6e9e3 to
e9cd55b
Compare
david-allison
commented
Jan 7, 2026
| <string name="basic_fields_tab_header" comment="Tab header for inserting non-special fields: {{Front}}">Basic</string> | ||
| <string name="special_fields_tab_header" comment="Tab header for inserting special fields: {{Deck}}">Special</string> | ||
| <string name="special_field_example_suffix"><![CDATA[: ‘<b>%1$s</b>’]]></string> | ||
| <string name="special_field_front_side_help">The front template content. Audio is not automatically played</string> |
| <string name="import_error_resolution_select_file">Open the file using your device’s file browser app</string> | ||
|
|
||
| <!-- Special Fields --> | ||
| <string name="basic_fields_tab_header" comment="Tab header for inserting non-special fields: {{Front}}">Basic</string> |
Member
Author
There was a problem hiding this comment.
Especially this - I feel I'm naming a new concept
EDIT:
The following are all better than 'Basic': I think 'Fields' makes sense
- Fields
- Normal
- Regular
- Standard
|
Look nice! I think the example tags should be something simpler like "Tag1 Tag2". I prefer "Normal" over "Basic". |
This introduces Anki's 'Special Fields' in the ViewModel
and adds a 'side' argument, so `{{FrontSide}}` can optionally
be displayed
This does not implement the user interface
See: https://docs.ankiweb.net/templates/fields.html#special-fields
david-allison
force-pushed
the
better-add-field
branch
from
e9cd55b to
33f7e3b
Compare
Member
Author
|
@ZornHadNoChoice The tags come from the note itself. I'd rather do this, over sending |
Improves discoverability of this feature vs needing to go through the manual Assisted-by: GPT-5.2: ViewPager2.updateHeight
This provides an explanation of all Special Fields to the user in the 'Insert field' dialog This also produces contextual help for all fields based on the context of the selected card/note (if any)
david-allison
force-pushed
the
better-add-field
branch
from
33f7e3b to
29902aa
Compare
5 tasks
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.
Purpose / Description
Anki has discoverability problems. One of the features which is unclear to users without reading the manual 'Special Fields': fields which relate to the metadata of the card.
{{Subdeck}}for example lists the current deckThis Pull Request updates the 'insert field' dialog to allows a user to select special fields. If the user came from 'manage note types' then the note type & card template have an example preview. If the user came from the note editor, then fields are populated based on the note ID, and the selected card template.
Approach
InsertFieldDialog: firstly just listing the special fields in a listHow Has This Been Tested?
Pixel 9 Pro
added template (no ord)
API 34 Tablet Emulator
Learning
Checklist