changed regex of problems to match exactly the output expected#38
Merged
Conversation
Collaborator
|
Yep. That makes sense. |
sethvincent
added a commit
that referenced
this pull request
Dec 10, 2014
changed regex of problems to match exactly the output expected
phillipj
added a commit
to nodeschool-no/javascripting
that referenced
this pull request
Jun 4, 2015
closes nodeschool-no/oversettere/workshopper#38
phillipj
added a commit
to nodeschool-no/javascripting
that referenced
this pull request
Jun 16, 2015
closes nodeschool-no/oversettere/workshopper#38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
How it's done at the moment, if you write your introduction.js challenge with the following:
it will say that's correct if you run
javascripting verify introduction.js. I think it's less confusing to check the exact output.