Add support for comment lines in Mocha options file #3370
Labels
area: usability
concerning user experience or interface
good first issue
new contributors should look here!
nice to have
enhancement proposal of low priority
Comments
outsideris
added
nice to have
plroebuck
added a commit
to plroebuck/mocha
that referenced
this issue
May 3, 2018
Modified code to strip comment lines, those beginning with a hash character ('#'), from "mocha.opts"
prior to processing its contents.
Fixes mochajs#3370
Bamieh
pushed a commit
that referenced
this issue
May 8, 2018
Modified code to strip comment lines, those beginning with a hash character ('#'), from "mocha.opts"
prior to processing its contents.
Fixes #3370
boneskull
pushed a commit
that referenced
this issue
May 18, 2018
Modified code to strip comment lines, those beginning with a hash character ('#'), from "mocha.opts"
prior to processing its contents.
Fixes #3370
sgilroy
pushed a commit
to TwineHealth/mocha
that referenced
this issue
Feb 27, 2019
Modified code to strip comment lines, those beginning with a hash character ('#'), from "mocha.opts"
prior to processing its contents.
Fixes mochajs#3370
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prerequisites
faqlabelRelated proposals:
#2587
#2870
#2963
Description
Add support for Beginning-of-Line (BOL) comments to "mocha.opts". As the file has far more in common with shell scripts (as it contains various Mocha cmdline arguments) than JavaScript tests, the comment character would be the hash ('#') character. Inline comments will not be supported.
Rationale
No current support for comment lines exists for "mocha.opts". With other related upcoming proposals for processing this file, the ability to document this file becomes more important than ever. Believe the other proposals got bogged down trying to do too much, arguing over more advanced features rather than providing the basics. As Larry would say, "Git 'Er Done".
The text was updated successfully, but these errors were encountered: