Closed dploeger closed 6 years ago
Hm. Travis didn't have that issue seemingly...
I'll try again to let it run locally, so I can add a test for the feature.
Okay, done. I basically just accepted the baseman tests, because the default description was already displayed there of course.
Hi, thanks for this PR!
A small problem is that default
could be falsy non-string value, we may need to update the condition.
And it would be nice if we add that case into tests.
I added some tests and optimized the non-string outputs. I think, it's fine this way. Booleans are reported as "false" or "true" and null is reported as "null".
Hm. Don't know, why travis fails. I don't think, it has to do with my modifications, though, because I didn't get the errors here.
@dploeger Hmm, it seems that some baseman reference files newly generated are added to this commit. Did you miss any?
Argh. Damn. I forgot to add the reference files to git. 🤦♂️
@dploeger Thanks! I may tweak the output format a little bit later, FYI.
This PR adds the default value of an option to its description, if one is specified.
However, I can not get the test suite to run.
I get the following errors when running
npm run build
: