-
Notifications
You must be signed in to change notification settings - Fork 9
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
fix: image migration issues #965
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👌
processor/utils.ts
Outdated
if (typeof attr.value === 'string' || attr.value === null) { | ||
memo[attr.name] = attr.value; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we intentionally want to set the attribute to null
here? May I ask why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't sure what to do with it. But I think it should actual set the value to true
This PR was released!🚀 Changes included in v7.5.1 |
🧰 Changes
Fixes some issues when migrating images.
mdast
was sometimes not correctly populating image attributes. I tried to make it more normal, so the attributes are copied to both the node and the hProperties. 🤷a
null
attribute could crash the transormers. I've added a null check, as well as filtered out empty attributes.🧬 QA & Testing
This should probably be tested in the main app so we get the full integrations.