-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
No error messages #1
Comments
Good to know, I'll have to think about how to best do this. l'm not sure where the error would be thrown, since data it's hard to know when data should or shouldn't be used. any thoughts? |
Well, the CLI version threw some kind of error when I tried it that way.
|
hmm, maybe it's how the context is being merged. can you put some code examples of what you did wrong and what worked? |
The error was that my YAML file had a comma where it oughtn't. I have a fairly standard .verbrc.md file with
However, no new README.md file was generated. Fully removing grunt verb
My Gruntfile doesn't have any particular config for verb, using the
|
Looks like the verb-cli loads data with plasma automatically, but I don't see that in grunt-verb so this could be the reason no error was being thrown. After you fixed it the data, does it create the README.md file correctly? |
Yep, once I figured out the error and fixed my YAML file everything was
|
ok, that was what I was wondering but didn't have a chance to check. so @doowb it sounds like plasma is throwing the error, which is a good thing. gives us a starting point, thanks |
So, today I ended up having an interesting issue. I'd changed my changelog, rebuilt my docs and everything was dandy ... except, the README file wasn't updated.
Doing a few tricks I figured out it's because I don't know how to YAML (whoops ...), but it would be very useful if grunt-verb could halt or toss out errors when there are such.
The text was updated successfully, but these errors were encountered: