[x] yes (bugfixes and features will not be merged without tests)
[ ] no
Breaking Changes?
[x] yes (breaking changes will not be merged unless absolutely necessary)
[ ] no
If yes, please include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.
List any relevant issue numbers:
Description
BREAKING CHANGES: the format of data-id in the output has changed.
This PR brings the important bits of md-to-react-email in house and removes react-email specific bits like data-id="react-email-*" and the peerDep in md-to-react-email on react-email. Overall this is a cleaner implementation for trying to differentiate the project and keep consistency.
If md-to-react-email pivots and becomes more generic, we can remove the code introduced in this PR (in /transform) and use a dependency again.
Component / Package Name:
This PR contains:
Are tests included?
Breaking Changes?
If yes, please include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.
List any relevant issue numbers:
Description
BREAKING CHANGES: the format of
data-idin the output has changed.This PR brings the important bits of
md-to-react-emailin house and removes react-email specific bits likedata-id="react-email-*"and the peerDep inmd-to-react-emailonreact-email. Overall this is a cleaner implementation for trying to differentiate the project and keep consistency.If
md-to-react-emailpivots and becomes more generic, we can remove the code introduced in this PR (in/transform) and use a dependency again.