Relative links to gitlab files about md2conf HOT 4 CLOSED

Today, relative links to resources that are not exported trigger an error because there would be no matching document in Confluence for the linked entity when the document tree is published as a series of wiki pages. However, there could be a configuration option or command-line switch to suppress unmatched link errors, and emit a warning message instead.

from md2conf.

A new configuration option --ignore-invalid-url has been added to skip relative URLs that point to locations not synchronized with the document or document tree. These will still show up as links in Confluence but will not navigate to another place (as if they were <a href="#">...</a>). A warning message will be emitted when these invalid links are encountered.

from md2conf.

md2conf already has a concept of base URL so we will need to clarify semantics. Currently, base URL means the root URL of a document tree, and md2conf maintains a catalog mapping (relative) URLs to Markdown documents. This is how md2conf makes sure that every document in the tree has a corresponding exported document in Confluence. If it were not for this catalog, there could be broken links.

On the other hand, I understand that you are asking for a different type of base URL, which would only apply to links that don't map as per the URL to Markdown catalog that md2conf maintains. Instead of ignoring these URLs, you would like them to be prefixed with a configured URL prefix to turn them into absolute URLs. They would appear as absolute URLs in Confluence wiki pages.

from md2conf.

Hey Levente,

Sorry to reopen this but would it be better to have an argument where you can specify a base URL for all relative links.
If for example we have a --base-url=http://mywebsite.com/something/ and a link in the markdown such as [.gitlab-ci.yml](.gitlab-ci.yml) the resulting link should be something like http://mywebsite.com/something/.gitlab-ci.yml

from md2conf.