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
Internal Markdown links don't work on codespaces #101203
Comments
Maybe #85105 |
Maybe. I've added repro steps here to compare |
Tested the fix using a local web build of VS Code. Codespaces may take a little time to pick this up |
Works with local build though.. 🤷♀️ |
GitHub Codespaces is on insiders from 3 days ago and still seeing this there. Version: 1.48.0-insider |
Thanks for testing @JacksonKearl. Yes I only tested with a local web build. Will see if I can figure out what is different about code spaces... |
Anyone working on this? Want to use for https://foambubble.github.io/foam/graph-visualisation |
For #101203 The current logic ends up tossing out the uri scheme and other important info when opening md links. This PR tries to avoid that
/fixedBy 830987e Should be working now (tested on VS Code docs) |
When I have a markdown file referencing another markdown file, and I follow the link whilst using codespaces on the web, it opens a new window containing only the text "Not Found", rather than opening the file within VSCode as expected.
Repro steps :
[How to contribute](CONTRIBUTION.md)
to the readmeExpected:
Contribution.MD loads in an editor window, as it does locally
Actual:
New window opens with text
Not Found
Filename in example is arbitrary, any relative link fails
The text was updated successfully, but these errors were encountered: