Skip to content
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

feat: filterMetaString option #58

Merged
merged 1 commit into from
Jan 8, 2023
Merged

feat: filterMetaString option #58

merged 1 commit into from
Jan 8, 2023

Conversation

atomiks
Copy link
Collaborator

@atomiks atomiks commented Jan 8, 2023

If the meta string also has custom config by you, it may cause issues with word highlighting or other features of rehype-pretty-code.

So Nextra would specify:

const options = {
  filterMetaString: (string) => string.replace(/filename=".*"/, ''),
};

@B2o5T

@netlify
Copy link

netlify bot commented Jan 8, 2023

Deploy Preview for rehype-pretty-code canceled.

Name Link
🔨 Latest commit 5bac4c1
🔍 Latest deploy log https://app.netlify.com/sites/rehype-pretty-code/deploys/63bae8f7561ef40008e6de56

@dimaMachina
Copy link
Contributor

Looks good, ty ❤️

@atomiks atomiks merged commit fe02098 into master Jan 8, 2023
@atomiks atomiks deleted the feat/filterMetaString branch January 8, 2023 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants