Fixed
Status Update
Comments
gh...@google.com <gh...@google.com>
pa...@google.com <pa...@google.com>
tn...@google.com <tn...@google.com>
tn...@google.com <tn...@google.com> #2
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Description
Just started using the TypographyQuotes lint check to replace our in-house built detector. However one case it doesn't catch is escaped strings.
E.g. the following does not raise a lint warning
but the following does:
Is this expected?
Tested with lint 8.1 alpha