Add pending spec for over-escaped multibyte source #95
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some customers have code with escaped multibyte characters in regular
expressions. This causes the engine to error because File.read doubly-escapes
it, which fails to parse.
The escaping these customers have is not needed. They can remove their
backslash and all should work fine. That's what we're prescribing for now via
customer services, since all other options are too time-consuming.
Eventually, we would like to support this code as-is (as we do any realistic
source files customers may have) -- when/if we do, this spec will pass.
/cc @codeclimate/review