-
Notifications
You must be signed in to change notification settings - Fork 19
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
Run fragment-check when internal
flag is true
#153
Conversation
03ea714
to
c23bf21
Compare
…ernal flag is active
c23bf21
to
ad99c47
Compare
…eck should already avoid irrelevant targets being in the set. Closes #152
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.
Good catch!
@@ -441,13 +449,68 @@ describe('hyperlink', function() { | |||
t | |||
); | |||
|
|||
expect(spyTapCalls(t.push), 'with set semantics to satisfy', [ |
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.
As I mentioned in https://gitter.im/unexpectedjs/unexpected?at=5d3475f2ec5abe7bbc227eab you should be able to use to have calls satisfying here
.
Co-Authored-By: Andreas Lind <[email protected]>
Fixes #152
When running with the
internal
flag or--internal
in the CLI, fragment checks were not run at all. Also not for completely site internal fragment links.