Skip to content

Conversation

@todor0v
Copy link

@todor0v todor0v commented Nov 15, 2025

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 ClientFeature component.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 15, 2025

Pull Request titles must follow the Conventional Commits specification and have valid scopes.

The subject "Lexical custom server feature not using absolute import path" found in the pull request title "docs: Lexical custom server feature not using absolute import path"
didn't match the configured pattern. Please ensure that the subject
doesn't start with an uppercase character.

feat(ui): add Button component
^    ^    ^
|    |    |__ Subject
|    |_______ Scope
|____________ Type

@todor0v todor0v changed the title fix(docs-rich-text-features): Lexical custom server feature not using absolute import path docs: Lexical custom server feature not using absolute import path Nov 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant