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
Let's say user would like to fetch a file from assets folder, but don't want to build full URL (maybe there is too many examples in assets, or they don't know on which domain will be the app deployed to).
If codeFromUrl pipe would support relative paths, it would be possible to reference the file only by a path which is starting from the assets folder. And that path would never change.
HighlightOptions interface might be enriched with baseUrl: string configuration option, where user could set the base path for relative URLs, e.g. https://example.com/my-app.
Use Case
This would allow to more easily reference files deployed on the same domain.
The text was updated successfully, but these errors were encountered:
Feature Description
When a relative URL is passed into
codeFromUrl
pipe, then file is not fetched.Let's say user would like to fetch a file from assets folder, but don't want to build full URL (maybe there is too many examples in assets, or they don't know on which domain will be the app deployed to).
If
codeFromUrl
pipe would support relative paths, it would be possible to reference the file only by a path which is starting from the assets folder. And that path would never change.HighlightOptions
interface might be enriched withbaseUrl: string
configuration option, where user could set the base path for relative URLs, e.g.https://example.com/my-app
.Use Case
This would allow to more easily reference files deployed on the same domain.
The text was updated successfully, but these errors were encountered: