This repository has been archived by the owner on Feb 7, 2024. It is now read-only.
feat: support lang on the meta #26
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc @antfu it'd super appreciate if you could give a look into this 🙇 |
antfu
changed the title
This was referenced Oct 30, 2023
Closed
5 tasks
antfu
added a commit
that referenced
this pull request
Nov 13, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR simply adds the current language to the
preNode properties. So that other rehype plugins can revisit the tree and do anything they might want to do / exposing the actual language doesn't do harm and should be included by default, imho.Linked Issues
Additional context
Adding the Language is definitely something that I believe should be part of the
preelement.