docs: Lexical custom server feature not using absolute import path #14628
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was following the instructions for adding a Lexical rich text custom feature and I had the problem that it was not showing in the admin panel within the Lexical editor. Following the Payload example, I noticed that an absolute path is used and the documentation (here) suggests a relative one. This fixed the issue.
Please let me know if I am mistaken or if there is a better way to suggest not using a relative path to the
ClientFeaturecomponent.