Bug Description
There is a jarring inconsistency in how .base views (like Tasks and Agenda) render labels for task properties.
While the standard Obsidian file list renders the properties correctly based on native display names and custom fieldMapping (e.g., showing "Wiederholung" and "Dateiname"), the interactive task cards completely ignore both the i18n-state-manager and the custom field mappings. Instead, they seem to use hardcoded English strings for their inline UI elements.
This issue also persists for the shortcuts to the views in the left sidebar.
When clicking the task its fully translated, the plugin menu also is fully translated as expected, but not the interactive tasks in the base view.
For example:
Even with uiLanguage set to de and fieldMapping heavily customized (e.g., due mapped to faellig, recurrence mapped to wiederholung), the interactive task card forcefully displays:
Due: Feb 23 (instead of Fällig)
Scheduled: Today (instead of Geplant)
Recurring: every 2 weeks... (instead of Wiederholung)
File.tags: #task and File.name:
Steps to Reproduce:
Go to Plugin Settings -> Set uiLanguage to de (or any non-English language).
Go to Advanced -> Modify fieldMapping (e.g., map due to faellig).
Create a task with a due date, scheduled date, tags, and recurrence.
Open a .base view (e.g., Agenda or Tasks default view).
Open the Properties panel on the right and check some properties to display them inline.
Observe: The interactive task UI ignores the translations and mappings, prepending hardcoded strings like "Due: ", "Scheduled: ", and "File.tags: ".
Expected Behavior:
The custom UI components rendering the interactive tasks should wrap their prefix labels in the i18n-state-manager's translation function (e.g., t('due')) and respect the display names of the properties, exactly like the standard file list does at the bottom of the exact same .base view.
If a user checks a property to be displayed in the bases view, it should not fallback to hardcoded strings like File.name: or File.tags:
Screenshots / Evidence:
comparison in the Agenda view where the top interactive tasks say "Due: / Scheduled: / Recurring:" while the raw files at the bottom correctly say "Wiederholung / Dateiname".
Environment:
TaskNotes Version: 4.4.0
Obsidian Version: 1.11.7
OS: Windows 11, Android 16
Bug Description
There is a jarring inconsistency in how .base views (like Tasks and Agenda) render labels for task properties.
While the standard Obsidian file list renders the properties correctly based on native display names and custom fieldMapping (e.g., showing "Wiederholung" and "Dateiname"), the interactive task cards completely ignore both the i18n-state-manager and the custom field mappings. Instead, they seem to use hardcoded English strings for their inline UI elements.
This issue also persists for the shortcuts to the views in the left sidebar.
When clicking the task its fully translated, the plugin menu also is fully translated as expected, but not the interactive tasks in the base view.
For example:
Even with uiLanguage set to de and fieldMapping heavily customized (e.g., due mapped to faellig, recurrence mapped to wiederholung), the interactive task card forcefully displays:
Due: Feb 23 (instead of Fällig)
Scheduled: Today (instead of Geplant)
Recurring: every 2 weeks... (instead of Wiederholung)
File.tags: #task and File.name:
Steps to Reproduce:
Go to Plugin Settings -> Set uiLanguage to de (or any non-English language).
Go to Advanced -> Modify fieldMapping (e.g., map due to faellig).
Create a task with a due date, scheduled date, tags, and recurrence.
Open a .base view (e.g., Agenda or Tasks default view).
Open the Properties panel on the right and check some properties to display them inline.
Observe: The interactive task UI ignores the translations and mappings, prepending hardcoded strings like "Due: ", "Scheduled: ", and "File.tags: ".
Expected Behavior:
The custom UI components rendering the interactive tasks should wrap their prefix labels in the i18n-state-manager's translation function (e.g., t('due')) and respect the display names of the properties, exactly like the standard file list does at the bottom of the exact same .base view.
If a user checks a property to be displayed in the bases view, it should not fallback to hardcoded strings like File.name: or File.tags:
Screenshots / Evidence:
comparison in the Agenda view where the top interactive tasks say "Due: / Scheduled: / Recurring:" while the raw files at the bottom correctly say "Wiederholung / Dateiname".
Environment:
TaskNotes Version: 4.4.0
Obsidian Version: 1.11.7
OS: Windows 11, Android 16