-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
0.9.0: related.list / toc problems #103
Comments
really? that's strange. marking as a bug |
do you have a global config? this would still be a bug, but is there a chance that verb is somehow merging your global config over the local config? Also, try using a $ verb --config=related.list:foo,bar,baz |
I believe i deleted them with But yea, I'll try in clean folder and no global config, and i'll back. |
Yea, still resets the https://asciinema.org/a/0xbhmy7egjfbacd8uapzbdllj (edit: 1) with |
Ok, that makes it easier thx. I was hoping it was just a glitch in verb itself, probably in the task logic or how the defaults are setup. This at least means that the global config isn't related to the issue |
@jonschlinkert do you know from where problem comes to navigate me so i can PR, cuz it is very weird. Moreover when I almost every day publish new package. ;d edit: because I maybe don't have time to debug. (saying "maybe" because I always say it that way but I always debugging and finding it ;d) |
it still does this?
No, not yet. But I suspect it comes from |
yea
ookey, i'll look what's up there, thanks |
I believe that the problem is somewhere here base-cli-process/index.js#L50-L58. It seems that the passed edit: in edit2: daaamn, i don't know ;d |
forget that, nothing related ;d |
ok, so the problem still exists, and we're not sure where it's happening? |
Yea, absolutely. Maybe the easy fix can be if we allow everything to be controlled through I was debugging few hours and didn't detect where the problem comes from. It may be in the |
Not sure for where the problem come, but i have
and when ran
verb --config related.list:...
it overrides the toc option totrue
.Again, not sure enough. Before didn't have such problems and don't know from when it is (if it is actual bug)
The text was updated successfully, but these errors were encountered: