Editable: Rename the Editable component, RichText component for clarity #4779
Conversation
youknowriad
added
[Feature] Rich Text
blocks/rich-text/editable.js
Outdated
| constructor() { | ||
| super( ...arguments ); | ||
| // eslint-disable-next-line no-console | ||
| console.warn( 'Editable is deprecated use wp.blocks.RichText instead.' ); |
There was a problem hiding this comment.
Minor: this sentence could use a period. :)
There was a problem hiding this comment.
It already use a period?
Edit: Oh! maybe you meant something like that:
"Editable is deprecated, use wp.blocks.RichText instead."
There was a problem hiding this comment.
Yes, I did. :) Sorry, should have been more specific :)
|
I'd be in favor of this change. |
youknowriad
force-pushed
the
update/rename-editable-rich-text
branch
from
8b5df6c
to
0282eb6
Compare
youknowriad
force-pushed
the
update/rename-editable-rich-text
branch
from
0282eb6
to
4069064
Compare
|
This change is important enough to make sure is noticed, cc @mtias @karmatosed. |
|
I updated the "Editable" label to "Rich Text". |
|
Is Editable still available as a name for backwards compatibility? Or do folks need to switch to RichText right away? Thanks!!! |
It's available and will be removed in like two or three releases ;) |
|
👌 |
refs #4776
This PR renames the
EditablecomponentRichTextto clarify that it's meant to be used for Rich Content exclusively and not as a replacement to inputs/textareas.We still export an
Editablecomponent for backwards compatibility with a warning asking people to useRichTextinstead.Next step will be to implement a
PlainTextcomponent and use it in one/two blocks. The blocks where we're currently usingTextareaAutosize.Testing instructions