language detection error
See original GitHub issueJust had the following output from commitlint, where it has incorrectly detected the language:
input: feat(commitlint-config-default): add default commitlint rules
⚠ commit must be in languague "eng", was one of: fra, cat, src, spa, sco [lang]
⚠ found 0 problems, 1 warnings
Running npx franc-cli "feat(commitlint-config-default): add default commitlint rules"
yields cat
as the result 😖
(Also note the minor typo in the error message)
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Detection of Language (Model) Errors - ACL Anthology
language models, in which some detection ... based on detecting errors of the language model. ... We evaluate individual features for error detection....
Read more >Automated Grammatical Error Detection for ... - Springer Link
It provides an overview of the automated approaches that have been developed to identify and correct these and other classes of learner errors...
Read more >Error detection in formal languages - ScienceDirect.com
An automaton that detects that errors have occurred in an input from a given language is merely a recognizer of that language. However,...
Read more >Error using langdetect in python: "No features in text"
Hey I have a csv with multilingual text. All I want is a column appended with a the language detected.
Read more >Turn on automatic language detection - Microsoft Support
The Detect language automatically option, available in Word and Outlook on Windows, detects the language that you are typing and automatically enables the ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for bringing the unknown constraints of development environments to the table, that rules out remote API usage.
My goal for
commitlint
is being as seamless aseslint
, possibly adding autofix capabilities and commit message suggestions in the very long run. Keeping around flaky rules will prevent the tool from achieving that.That being said I’d do this by deprecating them in some of the
2.x
releases by warning on stderr if they are used and remove them with the3.0
release the earliest.I just recently adopted
commitlint
, and thelang
andsubject-tense
rules result in false negative warnings for every commit. I’d definitely love to see them removed/improved, so that my commit lint runs were “clean”. Ideally, any error or warning would be actionable, so that they’re worth paying attention to.