-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Remark and rehype plugins #562
Remark and rehype plugins #562
Conversation
🦋 Changeset detectedLatest commit: c25ecff The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/pikapkg/astro-www/J2EDW3U51QRnE2CQKNQQwf5trs4x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks great! A few suggestions, but I think this is really close. Thanks for jumping right on this!
- Could you add a
.astro
page that usesimport { Markdown } from 'astro/components'
to the example here?
cc @matthewp if you could take a look at how the remark/rehype plugins are loaded that would be awesome. I feel like this might need to use the |
@natemoo-re thank you for the review, I wanted to make sure if I'm on the right way |
I left some comments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, will defer to @natemoo-re on any changes he thinks are important.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great!
Do you want to work on integrating these changes with import { Markdown } from 'astro/components';
in a .astro
file or would you be more comfortable if I did that?
@natemoo-re I would love to help with that. Should I add docs for the feature? |
@akellbl4 Awesome! Why don't you add some docs to this branch and I will add tests? I'm thinking about splitting |
3ff818d
to
c03a295
Compare
d16a64a
to
5851675
Compare
5851675
to
14c1fd9
Compare
@akellbl4 looks amazing—thank you SO much for all your work on this! I'm going to take care of the tests tomorrow and then this should be good to merge. |
@natemoo-re thank you for your help! It's pleasure to work on the project. |
- connect plugins by name - make plugins configurable - connect gfm and footnotes if no plugins provided from config - add more plugins to example
9f75910
to
c25ecff
Compare
@akellbl4 Docs look great and I added some tests to make sure there aren't regressions. Thanks again for getting this over the line, folks will be really excited about this feature! |
Awesome stuff! |
* remark plugins * remove unused dependency * enable codeblocks * backward compatibility with remark-code-titles * add support for rehype plugins * add proper types for plugins * fixes after review - connect plugins by name - make plugins configurable - connect gfm and footnotes if no plugins provided from config - add more plugins to example * update and rename example * add documentation for markdown plugins * chore: rename with-markdown-plugins example * chore: restructure dependencies * feat: add back smartypants, fix mdx expressions * chore: remove log * test: add markdown plugin tests * chore: add changeset * docs: update markdown doc Co-authored-by: Nate Moore <nate@skypack.dev>
Resolves #239
Changes
Testing
Docs