search

mlange-42 / yarner

Literate Programming command line tool for Markdown
https://mlange-42.github.io/yarner
MIT License
32 stars 1 forks source link

[Bug] Simplify block label paths when containing `..` #92

Closed mlange-42 closed 3 years ago

mlange-42 commented 3 years ago

E.g. this:

// <@experiments\../resources/random.md#file:src/resources/random.rs#0

should instead look like this:

// <@resources/random.md#file:src/resources/random.rs#0

(This kind of paths occurs through transclusions)

adamreichold commented 3 years ago

Isn't this closed via #93?

mlange-42 commented 3 years ago

Yes. It is linked to the MR, but probably GH closes it only when merged into master.

adamreichold commented 3 years ago

Yes. It is linked to the MR, but probably GH closes it only when merged into master.

Yeah, this is one of the mismatches between the assumptions coded into GitHub and git-flow. It might make sense to make dev the default branch though as master is basically used only to prepare releases anyway.

mlange-42 commented 3 years ago

I was already considering that, but was not sure if dev would then also be the branch displayed on the repo page as default. Actually, ma primary reason to still stick with git-flow is to always have the README etc. (incl. code) always represent the latest release rather than showing information that represents changes that are not released yet.

adamreichold commented 3 years ago

Actually, ma primary reason to still stick with git-flow is to always have the README etc. (incl. code) always represent the latest release rather than showing information that represents changes that are not released yet.

As with the multiple crates per repo issue, this could be resolved by publishing to crates.io which displays the README from the published crate version.

mlange-42 commented 3 years ago

But only on crates.io, not on GH 😉