Issue metadata
Sign in to add a comment
|
Blacklisting file from SpellChecker |
||||||||||||||||||||||||
Issue descriptionRun ID: 5739360200687616 Is it possible to blacklist a file from being run against SpellChecker? Due to how third_party/boringssl/crypto_test_data.cc is generated, linebreaks end up causing SpellChecker to report a number of words as misspelled.
,
Aug 8
The spellchecker should only check words in comments anyway (unless the file extension is not recognized). We fixed an issue yesterday with C++ file extensions but I don't believe that it's live yet. In any case, you bring up a good point, maybe the spellchecker shouldn't run on third party libraries. Could you share a link to the CL where this happened?
,
Aug 8
This happened on: https://chromium-review.googlesource.com/c/chromium/src/+/1167469 in the crypto_test_data.cc file.
,
Aug 8
We don't necessarily want to block tricium from running on anything in third_party, because there's third_party/blink and README files in third_party. I suspect blacklisting individual files isn't very scalable. Perhaps we just don't want to run on DEPS rolls like that change? Filed bug 872381 for that.
,
Aug 9
,
Aug 13
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by svaldez@chromium.org
, Aug 8