-
Notifications
You must be signed in to change notification settings - Fork 8
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
Needs a mechanism for replacing elements #7
Comments
#8 includes the mechanism by which this would be possible, but I think it’s a thing to look at once the features currently in it have landed! |
I accomplished this with
Then, I remap any instance of these tags so that the generated JSX uses my tags instead. I think this should also work for
What would make this super easy is having a way to inject imports for every file processed by the loader so one wouldn't have to have an |
That’s clever! I had been considering removing the “implicitly import React” option and replacing it instead with a method for defining imports which apply to all files which are processed. This would (hopefully!) allow for using this with Preact. The other thing of course is that it’s likely that Markdown Component Loader would need to be able to resolve paths to match where processed files are. I hope that’s not too difficult a job! I may have to investigate |
This would be a great enhancement! |
Should be possible to replace
<a>
s with<Link>
componentsThe text was updated successfully, but these errors were encountered: