-
Notifications
You must be signed in to change notification settings - Fork 920
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
[Feature request] Optionally allow invalid links in Markdown #1465
Comments
I also don't really know if it's something that should be done here or done in Vite itself. I assumed the former, as VitePress did it there as well. |
There is something you should know: images (and other assets like video and font) setting with local file path needed to be resolved and handled while packing. In another word, these must be valid:
These can be invalid as they are kept as is and not being resolved:
So in your case, you definitely could write image link with protocol or starting with /, the others like |
cc @meteorlxy I think we can support this to avoid broken relative image link stops the build process. |
Ummm... IMO the |
This issue is marked as |
Clear and concise description of the problem
Crowdin, a widely-known translation platform, has a certain configuration called "In-Context" translating. This essentially embeds a small JavaScript and a set of template strings that consist of string identifiers for Crowdin. You can read more about Crowdin's in-context translation setup here: https://developer.crowdin.com/in-context-localization/
However, when doing it this way, Crowdin generates links like this:
and this breaks compilation:
You can view an example of a project using this configuration here: https://github.com/cfw-guide/dsi.cfw.guide, where we temporarily worked around it with a hack.
Suggested solution
If possible, it would be nice to disable this open check, ideally for specific files.
I don't know at all if this is possible, as I don't really know enough JS to look around for ideas.
Alternative
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: