-
Notifications
You must be signed in to change notification settings - Fork 484
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
Caution against dynamic prettyurls
#2402
Conversation
Just a proposal to get things started. I have no particular attachment to any of the text. Feel free to tell me to change something, or directly push to the branch with whatever text you like. |
We should steer people away from using prettyurls = get(ENV, "CI", nothing) == "true" (or even `prettyurls = false`) and towards using `LiveServer`. It is best to have a consistent setting and to always use a webserver when viewing documentation locally. This avoids situations where there might be subtle difference with `prettyurls=true` or `prettyurls=false` and the documentation might work correctly when viewed locally, but be subtly broken (without an error message!) when deploying on GitHub Action. One such situation is a `@raw` block that references a local image. The correct relative path of that image would be different depending on the `prettyurls` setting.
face7ff
to
f8bd6ba
Compare
I'm actually kinda leaning towards just removing the
suggestion. Or maybe putting it in a |
34cc080
to
636089d
Compare
636089d
to
8d0dec7
Compare
Sounds good! Updated to https://documenter.juliadocs.org/previews/PR2402/man/guide/#Building-an-Empty-Document |
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.
LGTM, thank you @goerz!
We should steer people away from using
(or even
prettyurls = false
) and towards usingLiveServer
.It is best to have a consistent setting and to always use a webserver when viewing documentation locally. This avoids situations where there might be subtle difference with
prettyurls=true
orprettyurls=false
and the documentation might work correctly when viewed locally, but be subtly broken (without an error message!) when deploying on GitHub Action. One such situation is a@raw
block that references a local image. The correct relative path of that image would be different depending on theprettyurls
setting.Closes #2395