-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
md: enable custom anchor id/href for troubleshooting guide? #922
Comments
Would this imply using a special markdown syntax like ## [Too many open files error](#many-files) (and preventing the linking default)? If so, this seems probably too much to me. "Hardcoded" H2 elements is actually technically valid Markdown anyway. We just miss the nice anchor links – which could be hardcoded in as HTML/SVG as well, BTW. |
|
When you put it in a header Another idea, just: ## Probably long title #short-hash |
Found a bug on this. See #929 (review): |
@jorgeorpinel What browser? I can't reproduce this for some reason on my Mac |
Chrome on Mac but O_o this just went away after a force reload. Cache issue I guess, never mind! 😬 |
https://dvc.org/doc/user-guide/troubleshooting will have hardcoded H2 elements so we can choose the
id
to be short enough for error.dvc.org/{title} redirects (turned into URL hashes into this one page).It would be ideal if we could use markdown instead (
react-markdown
renders them with a nice anchor link), but we don't control theid
andhref
values in there, which tend to a little long.Implement a solution to this in our JS engine? Find a better workaround than hardcoded H2s?
The text was updated successfully, but these errors were encountered: