Handle a native angular minErr by deconstructing it #407
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.
Fixes GH-243
See: https://github.com/angular/angular.js/blob/v1.4.7/src/minErr.js
One thing to note, since I'm not entirely sure what we should do, is what the value inside
[..]
means.[ngPattern:noregexp]
would stand forngPattern
module, thennoregexp
is the type. As seen in https://github.com/angular/angular.js/blob/d077966ff1ac18262f4615ff1a533db24d4432a7/src/ng/directive/validators.js#L37-L40So what I'm doing is completely clobbering
stackInfo.name
with thisngPattern:noregexp
value, which hides the actualError
constructor type. Though, scrubbing the entire codebase of Angular, it doesn't appear that anyone leverages anything other than the defaultError
. But in theory, this API exists:minErr('$foo', TypeError)
and what I'm doing would clobber the fact that it was aTypeError
.