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
Is there a way to enable an entire category via my settings JSON? Ideally, I'm trying to enable all rules (and probably then disabling many of those rules), but I think there might be value in enabling them category by category.
As a very simple example, take a look at the IT_IS_OBVIOUS rule. It's not enabled by default, and it's not even enabled with picky enabled. However, if you explicitly enable IT_IS_OBVIOUS, then it ltex-ls will catch it.
IT_IS_OBVIOUS belongs to a group of one: The “Academic Writing” category with ID TON_ACADEMIC. But I can't enable the rule TON_ACADEMIC. I would think one would be able to enable/disable entire categories by their ID because I don't believe category names conflict with any of the rule names. Also, the LanguageTool CLI had the --enablecategories and --disablecategories options.
Is there something I'm missing?
The text was updated successfully, but these errors were encountered:
Is there a way to enable an entire category via my settings JSON? Ideally, I'm trying to enable all rules (and probably then disabling many of those rules), but I think there might be value in enabling them category by category.
As a very simple example, take a look at the
IT_IS_OBVIOUS
rule. It's not enabled by default, and it's not even enabled with picky enabled. However, if you explicitly enableIT_IS_OBVIOUS
, then it ltex-ls will catch it.IT_IS_OBVIOUS
belongs to a group of one: The “Academic Writing” category with IDTON_ACADEMIC
. But I can't enable the ruleTON_ACADEMIC
. I would think one would be able to enable/disable entire categories by their ID because I don't believe category names conflict with any of the rule names. Also, the LanguageTool CLI had the--enablecategories
and--disablecategories
options.Is there something I'm missing?
The text was updated successfully, but these errors were encountered: