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
It would be great if LT could enumerate all rule_id's for a language. It would make it easier to test every rule separately.
It is easy to get all rules from the XML; harder to get them from the collected java.
The text was updated successfully, but these errors were encountered:
Running each rule separately will mean a lot of overhead, as sentence splitting and POS tagging will need to run each time. So it's more efficient to run all rules and then extract the rule matches one is interested in.
I understand the overhead. But it is easier to have the previous for just one rule, and run only that rule and compare the output with the previous version for only that rule.
The formats of text output as well as Json output are quite inconvenient to handle if you are not a Java guy.
It would be great if LT could enumerate all rule_id's for a language. It would make it easier to test every rule separately.
It is easy to get all rules from the XML; harder to get them from the collected java.
The text was updated successfully, but these errors were encountered: