You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the doc website the top-right link Suggest an edit points to the master branch of the code.
Problem:
Some files don't exist in the master branch but do in previous stable releases of the crate.
How to reproduce:
In the Integrations page, all the the example links are broken, but also the Suggest an edit link! They all points to the master branch where the files they point to don't exist anymore.
Suggested solution:
I'm not sure about the authoring workflow for rinja, but since I was visiting the stable version of the docs (selected on the bottom left), links should point to the same stable version of the code, not master.
The text was updated successfully, but these errors were encountered:
Hello,
In the doc website the top-right link
Suggest an edit
points to themaster
branch of the code.Problem:
Some files don't exist in the
master
branch but do in previousstable
releases of the crate.How to reproduce:
In the Integrations page, all the
the example
links are broken, but also theSuggest an edit
link! They all points to themaster
branch where the files they point to don't exist anymore.Suggested solution:
I'm not sure about the authoring workflow for rinja, but since I was visiting the
stable
version of the docs (selected on the bottom left), links should point to the samestable
version of the code, notmaster
.The text was updated successfully, but these errors were encountered: