Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using `×` gives a `no-bare-strings` warning

See original GitHub issue

I think this is a bug. We also have things like   in the templates which do not output the warning. I glanced over the code for no-bare-strings and I couldn’t see where this is handled. But in any case, × should not give a no-bare-strings warning.

Issue Analytics

State:
Created 5 years ago
Comments:12 (9 by maintainers)

Top GitHub Comments

1reaction

rwjbluecommented, Nov 4, 2019

By the time our plugins run these html entity codes have been replaced by the underlying value that they represent (aka our plugin doesn’t know the difference between and at the moment).

This is actually fixed now. I think we can now properly ignore “HTML entity codes” (assuming that is what we want to do).

0reactions

rwjbluecommented, Feb 21, 2020

@boris-petrov - Hehe, the issue description definitely does not make that clear. 😄

Can you create a new issue that suggests something like “automatically allow all HTML entities in no-bare-strings rule”?