Skip to content
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

fix: fix nps init with config yml #182

Merged
merged 3 commits into from
Jun 23, 2018
Merged

Conversation

Hypercubed
Copy link
Contributor

What:

The nps init --type yml command is not working as expected.

How:

Change code to check for the same string as accepted by the parser.

@codecov
Copy link

codecov bot commented Jun 23, 2018

Codecov Report

Merging #182 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #182   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          12     12           
  Lines         386    386           
  Branches       93     93           
=====================================
  Hits          386    386
Impacted Files Coverage Δ
src/bin-utils/initialize/index.js 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ddca423...a0b2bf6. Read the comment docs.

@kentcdodds kentcdodds merged commit 5fc101d into sezna:master Jun 23, 2018
@krzycho1920
Copy link

.lookupSetter.proto["get arguments"].length

@Hypercubed Hypercubed deleted the fix/init-yml branch July 23, 2018 22:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants