This repository has been archived by the owner on Jul 29, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Throw an error in the launcher if the user sets an unknown flag #3216
Comments
Instead of throwing an error, should we warn the user that we encountered something unexpected? |
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 3, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 3, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 4, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 4, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 5, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 5, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 5, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 5, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 6, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 6, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 6, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 6, 2017
cnishina
added a commit
to cnishina/protractor
that referenced
this issue
Jan 6, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Some of our flags are very easy to mistype. Rather than silently ignoring unknown flags, we should at least show a warning and probably exit with an error if a user invokes Protractor with an unknown flag.
The text was updated successfully, but these errors were encountered: