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
Thus only the default version v3 (latest) works using the default sourcePath.
How can I get this to work? Here my example code, hosted on netlify.
I could not figure out my mistake from the docs and other issues. I'm guessing this issue is related to #244, #237 and #245. I could not understand any solution mentioned in those.
Issue-Label Bot is automatically applying the label question to this issue, with a confidence of 0.95. Please mark this comment with 👍 or 👎 to give our bot feedback!
How do I setup docute to work with git version tags?
Against intuition, the default behaviour seems to be that the version link is appended to the
sourcePaths
. For example, selectingv1
in the following code would resolve to https://raw.githubusercontent.com/sebinbenjamin/docute-demo/v1/README.md.However, the default case (latest/stable or master branch) would give a 400/404 error (https://raw.githubusercontent.com/sebinbenjamin/docute-demo/README.md). Thus I believe we cannot use it as above (without
overrides
).So I am thinking of using
overrides
onsourcePath
to solve this issue, but I do not understand how to proceed.In the above code, for some reason, I observe that
v1
as well asv2
./v1/
,/v2/
is getting appended to the commonsourcePath
, resulting in https://raw.githubusercontent.com/sebinbenjamin/docute-demo/master/v1/README.md which doesn't exist.Thus only the default version
v3 (latest)
works using the defaultsourcePath
.How can I get this to work? Here my example code, hosted on netlify.
I could not figure out my mistake from the docs and other issues. I'm guessing this issue is related to #244, #237 and #245. I could not understand any solution mentioned in those.
Any feedback on this is highly appreciated!
Update
docute/src/utils/index.js
Line 24 in c4d2bf9
overides
are not working.The text was updated successfully, but these errors were encountered: