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

Bug: Re-introduce the patch for syntax highlighting issues regarding C++ and F# #546

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

powersagitar
Copy link

@powersagitar powersagitar commented Mar 19, 2024

Tip

Please check out transitive-bullshit/nextjs-notion-starter-kit#605 for a bandaid fix before this PR gets merged.

Description

@transitive-bullshit mentioned in #220 that this fix was introduced with the release of v6, but apparently it vanished from master, thus the same issue still persists.

This PR re-introduces the patch to address syntax highlighting issues caused by Notion-prism.js language identifier mismatch.

Please refer to transitive-bullshit/nextjs-notion-starter-kit#309 and #220 for more context.

Notion Test Page ID

Before:
Screenshot 2024-03-19 12 03 32

After:
Screenshot 2024-03-19 11 58 14

https://powerium.notion.site/Decoding-Conditionals-A-Dive-into-if-else-switch-case-Lookup-Tables-and-Interfaces-19254846bcb64aac9c340e81518a9dac

Copy link

vercel bot commented Mar 19, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
react-notion-x ✅ Ready (Inspect) Visit Preview Mar 19, 2024 4:09pm
react-notion-x-minimal-demo ✅ Ready (Inspect) Visit Preview Mar 19, 2024 4:09pm

@powersagitar powersagitar changed the title Bug: Fix syntax highlighting issues for C++ and F# Bug: Re-introduce the patch for syntax highlighting issues regarding C++ and F# Mar 19, 2024
@rimonhanna
Copy link

@transitive-bullshit

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