-
-
Notifications
You must be signed in to change notification settings - Fork 399
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
Yard graph with alternate db fails #583
Comments
YARD doesn't generate doc unless you use |
FYI approach #1 breaks the API because it changes behaviour; we can't do that. I'm pretty sure there are uses of |
No worries. Is approach 2 ok then? That or we keep |
Yea loading afterwards seems like it should be fine. If it passes all tests I can merge. |
Sorry - the Ambiguity of the Internet strikes. |
Yes, #585 looks good as long as it's passing :) still have to test it on other environments though. |
Referencing #589 here for clarity when you look at the pull request. |
I have been pretty busy for the last month, but things are winding down. I'll have a change to check this over and put out a release this weekend. |
No worries. Pretty much the same story for me too :) |
Similar to #580,
yard graph --db <alternate-dir>
doesn't work either.Easily solved though. I'll submit 2 separate pull requests, one big-picture; one isolated. Choose whichever makes you happier. :)
Note though: I strongly dislike having Yard contribute two directories of purely generated data to my project root (
.yardoc
anddoc
). Other projects like to do the same and the end result is about 500 (possibly exaggerated) directories, some valuable, some transient - it all becomes very messy and strains minds and the housekeeping cost.I therefore love that Yard supports me moving this stuff around - it just seems like the functionality hasn't been very well tested yet. THUSLY I'll likely be raising more issues around this so...
TL;DR I recommend my patch to
Registry
so that other pieces of Yard functionality I haven't come across yet but have a similar issue, have a chance of being fixed simultaneously.The text was updated successfully, but these errors were encountered: