You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many of our localization strings are located in the same file, but organized within this file by kind of namespacing pattern, let's say Domain.Task, Domain.TaskId, General.Ok, General.Cancel, SomeSpecialDialog.InfoTooltip
With this pattern I often filter the key column by the namespace prefix when adding entries. Let's say I'm working on SomeSpecialDialog, then a column filter to "SomeSpecialDialog." is handy to scope the view to all items of interest.
Applying that filter and adding the first new key currently removes the filter again. This is a useful approach whenever the filter doesn't match the new key - as the new item would not be visible at all.
If it is (as in the workflow described above) it shouldn't be necessary to clear the filter.
So I propose to only delete the filter of the key column if it doesn't match the key just created.
(for reference in case someone without deep knowledge to the code - as myself - works on it: ccda729 seems to be a good starting point, that's the commit where clearing the filter was introduced).
The text was updated successfully, but these errors were encountered:
Many of our localization strings are located in the same file, but organized within this file by kind of namespacing pattern, let's say Domain.Task, Domain.TaskId, General.Ok, General.Cancel, SomeSpecialDialog.InfoTooltip
With this pattern I often filter the key column by the namespace prefix when adding entries. Let's say I'm working on SomeSpecialDialog, then a column filter to "SomeSpecialDialog." is handy to scope the view to all items of interest.
Applying that filter and adding the first new key currently removes the filter again. This is a useful approach whenever the filter doesn't match the new key - as the new item would not be visible at all.
If it is (as in the workflow described above) it shouldn't be necessary to clear the filter.
So I propose to only delete the filter of the key column if it doesn't match the key just created.
(for reference in case someone without deep knowledge to the code - as myself - works on it: ccda729 seems to be a good starting point, that's the commit where clearing the filter was introduced).
The text was updated successfully, but these errors were encountered: