-
-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: angular pattern escape problem #153
Conversation
蒋津 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. |
Codecov Report
@@ Coverage Diff @@
## master #153 +/- ##
==========================================
- Coverage 96.96% 96.03% -0.94%
==========================================
Files 2 2
Lines 99 101 +2
Branches 20 20
==========================================
+ Hits 96 97 +1
- Misses 3 4 +1
Continue to review full report at Codecov.
|
Have sign CLA. Is the name must github user? |
index.js
Outdated
@@ -129,6 +129,9 @@ module.exports = function(content) { | |||
} | |||
|
|||
if(config.interpolate && config.interpolate !== 'require') { | |||
content = content.replace(/(ng-)?pattern=(["']?\/((?:.(?!["']?\s+(?:\S+)=|[>"']))+.)\/["']?)/g, function (pattern, $1, $2) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it instead be possible to ignore ng-*
in general ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Support ng-* pattern at new commit
@jinker The email address used for your github account and the email address used in |
Closing in favor of #154 |
angular pattern escaped character conversion problem
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Does this PR introduce a breaking change?
If this PR contains a breaking change, please describe the following...
Other information: