-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Question]: Is there OOB support for text editor? #10320
Comments
Hi @lordsfantasy thanks for opening this issue! To answer your question, we don't have a component for that. The pattern was actually contributed by a community member here: #2447 We were interested in the component for sure, but don't have the bandwidth/priority for it, so we just added it as a pattern. We'd love to have someone contribute the code for it. |
Hey @jnm2377, thanks for sharing the #2247. It was super fun going through the backstory and how it evolved into the pattern that it is today. We used draftjs in our project and modified its design as per the text toolbar pattern. I wouldn't say we achieved 100% design though. The carbon text toolbar pattern functionality seems so much more polished and thoughtfully designed. If we have to contribute the code, how should we go about it? What should be the underlying editor? |
@lordsfantasy To my knowledge we don't have any data surrounding teams' usage of editor solutions. It would be a total shot in the dark. I think it would be ideal for the components to not be tied to any specific editor. We could potentially bring in an editor in the storybook environment to wire it all up as an example though. |
Correct, most of our patterns do not have code tied to them and they are mostly mean for design guidelines and best practices. Going to close 👍 |
Question for Carbon
Does carbon provide the following component/pattern?
https://www.carbondesignsystem.com/patterns/text-toolbar-pattern/
Or the above article is more like a guideline to the designer?
Code of Conduct
The text was updated successfully, but these errors were encountered: