Skip to content
This repository was archived by the owner on Nov 2, 2023. It is now read-only.

Conversation

adamvoss
Copy link
Contributor

New additions on this page keep following style of existing links rather than the more concise Markdown syntax even though I doubt there is specific need to be able to anchor the page to the new link. This changes all the links to Markdown syntax to try to change the syntax used by new additions.

This does remove the ability to anchor the page to a specific link, possibly breaking the anchoring of existing external links. However, I doubt there is much that depends on this functionality. Additionally, I would argue if you are trying to link directly to an implementation's link, likely could just link directly to the implementation's site.

Method of implementation: Find and Replace
Find: <a href="(.*?)".*?>(.*)</a>
Replace: [$2]($1)

@handrews
Copy link
Contributor

Additionally, I would argue if you are trying to link directly to an implementation's link, likely could just link directly to the implementation's site.

Yeah, agreed, thanks for doing this! I'm halfway through auditing all of these to see what's still active and who is working on draft-06 support. Which has nothing to do with this PR, just commenting so you know that's going on.

@handrews handrews merged commit 78336b9 into json-schema-org:master May 26, 2017
@adamvoss
Copy link
Contributor Author

adamvoss commented Jun 6, 2017

Happened to figure out why the links had been done that way. Looks like it was at one time to get Google Analytics to track which links were accessed 3b34df9.

@adamvoss adamvoss deleted the markdownify branch June 7, 2017 15:36
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants