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

Revert "Fix hashtag regex blocking transform to heading" #5636

Merged
merged 1 commit into from
Feb 20, 2024

Conversation

acywatson
Copy link
Contributor

@2wheeh

Unfortunately, I made a mistake here - some Meta surfaces support multiple leading "#" characters in a hashtag, so this would break them. Instead, we might need a generic way to override the regex.

Reverts #5376

Copy link

vercel bot commented Feb 20, 2024

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

Name Status Preview Comments Updated (UTC)
lexical ✅ Ready (Inspect) Visit Preview Feb 20, 2024 4:00pm
lexical-playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 20, 2024 4:00pm

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Feb 20, 2024
Copy link

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
packages/lexical/dist/Lexical.js 26.67 KB (0%) 534 ms (0%) 207 ms (+7.36% 🔺) 740 ms
packages/lexical-rich-text/dist/LexicalRichText.js 38.8 KB (0%) 776 ms (0%) 274 ms (-12.54% 🔽) 1.1 s
packages/lexical-plain-text/dist/LexicalPlainText.js 38.77 KB (0%) 776 ms (0%) 337 ms (+35.39% 🔺) 1.2 s

@acywatson acywatson merged commit 4792ff6 into main Feb 20, 2024
39 of 45 checks passed
@acywatson acywatson deleted the revert-5376-hashtag-regex branch February 20, 2024 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants