Skip to content

feat: support numeric priority values#1691

Open
Moyf wants to merge 1 commit intocallumalpass:mainfrom
Moyf:feature/numeric-priority-support
Open

feat: support numeric priority values#1691
Moyf wants to merge 1 commit intocallumalpass:mainfrom
Moyf:feature/numeric-priority-support

Conversation

@Moyf
Copy link

@Moyf Moyf commented Mar 11, 2026

Try to close #1289

I had the AI write it, and after finishing, I roughly reviewed the changes it made.
Then I realized the amount of changes involved is indeed quite substantial, and I understand the difficulty of this requirement now. 😅

However, most of the changes are type conversions—which, in a way, is quite suitable for AI to handle ;)

This PR is just a reminder and is not urgent to merge. I’ll test it locally for a while to see if it works properly.

Also, if anyone else is interested in the priority of numeric types, feel free to give it a try. Salute!


  • Add support for both string and number types in priority values
  • Add 'Priority value type' setting to choose output format (text/number)
  • FieldMapper converts priority to chosen format when writing frontmatter
  • Default to text values for backward compatibility
Snipaste_2026-03-11_14-28-49

- Add support for both string and number types in priority values
- Add 'Priority value type' setting to choose output format (text/number)
- FieldMapper converts priority to chosen format when writing frontmatter
- Default to text values for backward compatibility
- Remove unnecessary String() conversions on label fields
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.

[FR]: Allowing setting "Priority" property's type to Number

1 participant