Skip to content

Conversation

@DDeenis
Copy link
Contributor

@DDeenis DDeenis commented Feb 1, 2026

Resolves #562

MarkdownText component processes and shrinks the passed text, so we can't really know if it's empty or not on the outside, which breaks some conditional logic.
Since the actual rendering logic is quite simple (dumping html into a span), using a composable instead allows to correctly evaluate if the processed string is empty or now.

@vercel
Copy link

vercel bot commented Feb 1, 2026

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

Project Deployment Actions Updated (UTC)
npmx.dev Ready Ready Preview, Comment Feb 1, 2026 1:13pm
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
docs.npmx.dev Ignored Ignored Preview Feb 1, 2026 1:13pm
npmx-lunaria Ignored Ignored Feb 1, 2026 1:13pm

Request Review

@danielroe
Copy link
Member

maybe a good candidate for some unit tests?

@DDeenis
Copy link
Contributor Author

DDeenis commented Feb 1, 2026

Apologies, forgot to update tests. Will do in the morning.

@DDeenis
Copy link
Contributor Author

DDeenis commented Feb 1, 2026

Need some more fixes to do

@danielroe
Copy link
Member

I this one was introduced by 57975af

@DDeenis
Copy link
Contributor Author

DDeenis commented Feb 1, 2026

Nah, I just missed the a11y test file still referencing MarkdownText.vue

@DDeenis
Copy link
Contributor Author

DDeenis commented Feb 1, 2026

Nothing happened at MarkdownText.vue in January 2026

@danielroe danielroe enabled auto-merge February 1, 2026 13:14
@danielroe danielroe added this pull request to the merge queue Feb 1, 2026
Merged via the queue into npmx-dev:main with commit 592982d Feb 1, 2026
13 checks passed
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.

Incorrect markdown parsing in package description

2 participants