-
Notifications
You must be signed in to change notification settings - Fork 7
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
Compatibility with Documenter 1.0 #3
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests pass and docs build, but some things don't quite work yet.
I’ll have a look at these (on my phone right now). As a heads-up: I already adapted the documentation this morning, and I’ll push that branch and make a PR later today. |
This is the least important aspect of this PR, but just for the record: To get the "Codestyle" CI to pass, run
The relevant rules are in the |
f40c284
to
136fecf
Compare
Okay, this branch is ready now I think but let's leave it unmerged until Documenter is released. Users that want to use Documenter#master can use this branch for now. |
136fecf
to
10e0053
Compare
Looks like this branch does not expand citations in docstrings. I wonder if the order within documenter have changed. |
@mortenpi it looks like the tree iterator here doesn't reach all the way to the docstrings now, but stop at |
Thanks so much for helping with adapting this to the upcoming Documenter release, guys!
Yes, let's slow down with this a little for now, if that's ok… Especially because I gotta go and work on my JuliaCon talk for a bit 😉. But after that, I'll need to get my head back into the internals and look through everything in detail. I'd like to add a test that the issue that I described in https://discourse.julialang.org/t/running-makedocs-overwrites-repl-docstrings/95982 is gone with the new Documenter version, and that the workaround in DocumenterCitations.jl/src/DocumenterCitations.jl Lines 21 to 28 in 7b235fd
is no longer necessary. That is, one can hopefully run I'd also want to think through the implications of #6 for how exactly |
You need to explicitly dive into the E.g. something like what is done here: https://github.com/JuliaDocs/Documenter.jl/blob/7c97a86a31e360d7d22082a9a783b0cab24163b5/src/CrossReferences.jl#L31-L53 This should eventually be changed though, and the docstrings should become proper child nodes. |
Just a heads-up: I was able to rebase this on top of #32 and make further modifications that get everything working perfectly with today's This includes expanding citations in docstrings. The caching workaround is no longer needed. Also, #19 solved itself 🎉. Not sure yet about #16. I'll wait with force-pushing the changes to this PR until after #32 is merged (stacking more than two PRs just gets a little too messy). In any case, I think I can take it from here, and there shouldn't be any problem whatsoever with being compatible with Documenter 1.0 as soon as it's released. Thanks again for helping me to get the conversion started! |
Great, thanks. Wanted to pick this up but didn't find the time. |
10e0053
to
2033590
Compare
@fredrikekre @mortenpi Congratulations on the Documenter 1.0 release! I would still like to merge #35 first and make a 1.1 release based on that (still compatible with Documenter 0.27). But after that, this PR should be ready to merge, and would then be the 1.2 release. There is of course a "breaking change" in that the plugin now has to be passed to Two small details that still need to be fixed in this PR:
|
7b773f0
to
a4aa02a
Compare
Ok, fixed those two remaining issues… This should now be ready for final review. It would still have to be rebased after merging #35 and making the 1.1 release. |
Oh, and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't approve my own PR but looks good.
Agreed, this is a change in Documenter's interface, not DocumenterCitations'. Documenter users should have an explicit compat on Documenter to avoid any issues with this. |
a4aa02a
to
2217636
Compare
2217636
to
e0bacb7
Compare
This patch updates the code base so that it works with the breaking release of Documenter 1.0.
e0bacb7
to
5a66543
Compare
Edit (@goerz):
As a side-effect:
Closes #19