Skip to content

[lexical-markdown] Bug Fix: Prevent Markdown links with empty string link text from being automatically removed#7923

Merged
etrepum merged 1 commit intofacebook:mainfrom
adambolcsfoldi:bug-fix-prevent-markdown-empty-link-text-from-disappearing
Oct 17, 2025
Merged

[lexical-markdown] Bug Fix: Prevent Markdown links with empty string link text from being automatically removed#7923
etrepum merged 1 commit intofacebook:mainfrom
adambolcsfoldi:bug-fix-prevent-markdown-empty-link-text-from-disappearing

Conversation

@adambolcsfoldi
Copy link
Copy Markdown
Contributor

@adambolcsfoldi adambolcsfoldi commented Oct 14, 2025

Description

Currently any markdown link where the link text is an empty string, e.g. [](https://lexical.dev), will be automatically removed.
With this pull request, the link persists allowing for further editing.

Test plan

Before

Before.Link.disappears.mov

After

After.Link.stays.mov

@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Oct 14, 2025

Hi @adambolcsfoldi!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@vercel
Copy link
Copy Markdown

vercel bot commented Oct 14, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
lexical Ready Ready Preview Comment Oct 17, 2025 7:33am
lexical-playground Ready Ready Preview Comment Oct 17, 2025 7:33am

@adambolcsfoldi
Copy link
Copy Markdown
Contributor Author

A CommonMark Spec compliant but ultimately less useful fix was discussed and rejected here: #7919

@etrepum
Copy link
Copy Markdown
Collaborator

etrepum commented Oct 14, 2025

You will need to accept the CLA before merging your PR can be considered.

@meta-cla meta-cla 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 Oct 16, 2025
@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Oct 16, 2025

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@adambolcsfoldi
Copy link
Copy Markdown
Contributor Author

You will need to accept the CLA before merging your PR can be considered.

Done! Sorry for the delay.

@etrepum
Copy link
Copy Markdown
Collaborator

etrepum commented Oct 17, 2025

No need to rebase or update unless there's a conflict, that just slows things down (CI has to run again)

@etrepum etrepum added this pull request to the merge queue Oct 17, 2025
Merged via the queue into facebook:main with commit cb828fc Oct 17, 2025
39 checks passed
This was referenced Oct 27, 2025
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. extended-tests Run extended e2e tests on a PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants