Resolve relative paths to files about cosmere

[mihaeu]

So what I meant was something like ```md See [doc](doc.md) ``` If doc.md is also mirrored to confluence then I don't want them link to the file I want the link to the confluence page. El lun, 7 feb 2022 17:51, codethief ***@***.***> escribió:

…

Hmm I'm not sure I see the use case yet. What stops you from linking the Github URL directly in your Markdown files? I think what you're having in mind is a general way to re-write anchor links. That might definitely be useful but I think as a very first step I would focus on getting relative links (to other pages handled by Cosmere) right. — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQRO7ONMV5JD6TPQXF4H2LUZ7Z7TANCNFSM4XAR6HJA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were assigned.Message ID: ***@***.***>

[mihaeu]

Brainstorming:

if the relative link target is in the cosmere config
   generate a link to that confluence page
else if the relative link is part of the repository
  generate a link to the repository
else
  ???
``

[codethief]

Automatically converting links to relative paths would indeed be a very nice feature! I would give this a shot and try to come up with a patch, but so far I haven't been able to figure out where in the code links get converted. Could you give me a pointer?

else if the relative link is part of the repository
generate a link to the repository

Which repository are you referring to?

[mihaeu]

Hi @codethief

So I was assuming (based on how I use it and how I've seen others use it) that people keep their markdown files in a git repository.

So case 1 would be a lookup in the cosmere.json config. Case 2 would be a lookup in the repository that contains the file itself. An example might be that you're linking to a file in your codebase, e.g. package.json or pom.xml which will be lost in Confluence. But to really make these links useful, they would have to point to the repository. So maybe <a href="https://github.com/mihaeu/cosmere/package.json">...</a>, but the question is where to get the base URL from. It could be guessed from the git remote, but that's not reliable because if it's ssh then it's hard to extrapolate the URL from that. I think it would have to be another setting in the cosmere.json. Another option would be to lookup the property from the package.json. It's already in there, but I've also seen people use cosmere from a Docker container, globally or without really installing it using npx and then there wouldn't be a package.json to refer to.

Long story short: I guess a first step would be a simple config lookup. Step two could be adding a new field to the config and printing warnings if there are relative links that cannot be resolved.

And to make things even more complicated it would be nice if anchors would be resolved properly, because afaik that's not working properly right now.

[codethief]

Hmm I'm not sure I see the use case yet. What stops you from linking the Github URL directly in your Markdown files? I think what you're having in mind is a general way to re-write anchor links. That might definitely be useful but I think as a very first step I would focus on getting relative links (to other pages handled by Cosmere) right.