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
Now that the InfoMapper has been switched to path location strategy, I want to update markdown files that are used to not use has in the URL. However, this is not working, at least locally in the development environment. An old link looked like:
See also [***Release Notes***](#/content-page/release-notes).
A new link looks like the following (I tried with and without leading slash):
See also [***Release Notes***](/content-page/release-notes).
See also [***Release Notes***](content-page/release-notes).
The first link gives the following (note the duplicate content-page, but one is singular and one is plural):
The second link gives the following:
The good news is that the old hash location URLs do automatically convert to the new path location URLs. However, I need to know what the proper syntax is to include in Markdown content pages to work. This will also be used with all of the info popups.
It may also make sense in the application to handle converting hash to path and the other way around, depending on what the application uses. I'm not sure we'll ever go back to hash location strategy but don't want to lose track of how that might work. The default can be path location strategy.
The text was updated successfully, but these errors were encountered:
There was a small bug in the code now that the hash is not being used, and that has been fixed. So all links will work at the moment, but because of the Showdown property openLinksInNewWindow being set, it considers internal links to other "pages" in the app to be external and will open it in a new tab as well.
I new issue has been created on the Showdown Github page and we are waiting to hear back from them.
Now that the InfoMapper has been switched to path location strategy, I want to update markdown files that are used to not use has in the URL. However, this is not working, at least locally in the development environment. An old link looked like:
A new link looks like the following (I tried with and without leading slash):
The first link gives the following (note the duplicate
content-page
, but one is singular and one is plural):The second link gives the following:
The good news is that the old hash location URLs do automatically convert to the new path location URLs. However, I need to know what the proper syntax is to include in Markdown content pages to work. This will also be used with all of the info popups.
It may also make sense in the application to handle converting hash to path and the other way around, depending on what the application uses. I'm not sure we'll ever go back to hash location strategy but don't want to lose track of how that might work. The default can be path location strategy.
The text was updated successfully, but these errors were encountered: