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

feat: add element override for text nodes #42

Merged

Conversation

zallek
Copy link
Contributor

@zallek zallek commented Apr 6, 2022

Fixes #41.

Purpose

Make the lib compatible with Google Translate

Approach and changes

Allow overriding normal text component (cf issue for more details)

Deps upgrades

  • @sumup/foundry: Needed because the locked version was using a beta version of semantic-release that is not available on npm anymore -> will fix master CI build.
  • @contentful/rich-text-types: use latest version (no break changes)

@zallek
Copy link
Contributor Author

zallek commented Apr 12, 2022

Hey @connor-baer Would you have time to review this PR pls?

Copy link
Owner

@connor-baer connor-baer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you so much for the contribution, @zallek! 🙌

I will make a few more updates and will release a new version of the package shortly.

@connor-baer connor-baer changed the title Feat/41 google translate compatibility feat: add element override for text nodes Apr 15, 2022
@connor-baer connor-baer merged commit 52810bf into connor-baer:master Apr 15, 2022
@github-actions
Copy link
Contributor

🎉 This PR is included in version 2.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot added the released This change has been released label Apr 15, 2022
@zallek
Copy link
Contributor Author

zallek commented Apr 19, 2022

Thanks a lot :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released This change has been released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants