-
Notifications
You must be signed in to change notification settings - Fork 15
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: [FX-4053] move rich text editor to a separate package #3637
Conversation
🦋 Changeset detectedLatest commit: 18f042b The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@toptal-bot run package:alpha-release |
8c7e408
to
e2980e9
Compare
@toptal-bot run package:alpha-release |
Your alpha package is ready 🎉 |
@toptal-bot run package:alpha-release |
Your alpha package is ready 🎉 |
9e3492e
to
9322503
Compare
46afb3b
to
e1da28e
Compare
@toptal-bot run package:alpha-release |
Your alpha package is ready 🎉 |
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.
Looks good!
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.
It looks like everything is working, didn't catch any possible errors
* chore: create codemods for rte * chore: adjust codemod * chore: update eslint rules for codemod * chore: update eslintignore * chore: update prettier ignore * chore: update version
b233965
to
6e657b2
Compare
FX-4053
Description
We have to move RTE to a separate package to provide customers more flexibility
How to test
Use this PR to test
Development checks
Breaking change
PR commands
List of available commands:
@toptal-bot run package:alpha-release
- Release alpha version@toptal-anvil ping reviewers
- Ping FX team for reviewPR Review Guidelines
When to approve? ✅
You are OK with merging this PR and
nit:
to your comment. (ex.nit: I'd rename this variable from makeCircle to getCircle
)When to request changes? ❌
You are not OK with merging this PR because
When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:
How to handle the comments?