Usage report and contexts giving a lot of false positives.

When getting a usage report, it is complaining about all contexted keys. I’ve added _plural to my Derived Key Rules setting to avoid most of them, but for custom contexts it seems like they have to be added manually.

Let’s say I have the following keys:

"match": "Match"
"match_plural": "Matches"
"match_count": "{{count}} match"
"match_count_plural":  "{{count}} matches"
"match_numbered": "Match number {{number}}"

The usage report would mark the lower three ones as unused even if they are used in the code and targeted through { context: “numbered” } (or similar).

I tried but haven’t got either regex or glob matching to work for keys containing _ but didn’t succeed.

This might be possible somehow and I’m just missing it.

[antfu]

Continues in #570

[bratzie]

Thank you for the reply! 😃

I’m using that already for some base cases (like _plural and _0 (and so on)). I think what would solve this issue in a broader sense would be adding something like a checkbox setting that said “ignore keys with underscore ( _ ) in Usage Report”.

With the current implementation I don’t think usage report understands if context is used, so if you use context a lot, you would have to add every unique context to the Derived Key Rules to have any use of the usage report feature.