With the 250,000+ dictionary rules, serialising all the rules to HTML uses all the available memory when we load the /rules page in the Checker service. The Rule Manager shows us all rules already, and we don't want to solve this problem in both apps.
Instead, only show the total rules per category in the Checker. This should give us confidence that the correct number of rules are published for each category (e.g. subcategories of style guide rules, language tool rules, dictionary rule).
In the future it may be a good idea to include some kind of artefact id in the Checker, in order to verify that a new artefact from the Rule Manager has been properly ingested by the Checker.
How to test
Run the Checker service according to the instructions in the readme.
If there is a table with total rules per category there, including dictionary rules (probably reported as 'Typos'), this branch is working as expected.
If not, run the Rule Manager service, make sure dictionary rules have been created (by hitting the api/refreshDictionary endpoint). Then check the /rules page in the Checker again.
With the 250,000+ dictionary rules, serialising all the rules to HTML uses all the available memory when we load the
/rulespage in the Checker service. The Rule Manager shows us all rules already, and we don't want to solve this problem in both apps.Instead, only show the total rules per category in the Checker. This should give us confidence that the correct number of rules are published for each category (e.g. subcategories of style guide rules, language tool rules, dictionary rule).
In the future it may be a good idea to include some kind of artefact id in the Checker, in order to verify that a new artefact from the Rule Manager has been properly ingested by the Checker.
How to test
api/refreshDictionaryendpoint). Then check the/rulespage in the Checker again.