Skip to content
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

useLexicalDrawer hook needs to be exported #9135

Open
ritesht opened this issue Nov 12, 2024 · 1 comment
Open

useLexicalDrawer hook needs to be exported #9135

ritesht opened this issue Nov 12, 2024 · 1 comment
Labels
status: needs-triage Possible bug which hasn't been reproduced yet v3

Comments

@ritesht
Copy link

ritesht commented Nov 12, 2024

Describe the Bug

In order to extend richtext-lexical more specifically for experimental table support feature, useLexicalDrawer is required but isnt exported. Other features seem to be using it as well fairly frequently. Can this be added to client exports please? Currently blocked because of this.

Link to the code that reproduces this issue

https://github.dev/payloadcms/payload/blob/beta/packages/richtext-lexical/src/index.ts

Reproduction Steps

  1. Open packages/richtext-lexical/src/exports/client/index.ts
  2. useLexicalDrawer is missing from the exports

Which area(s) are affected? (Select all that apply)

plugin: richtext-lexical

Environment Info

Payload beta 124-128
@ritesht ritesht added status: needs-triage Possible bug which hasn't been reproduced yet v3 validate-reproduction labels Nov 12, 2024
Copy link

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@beta -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs-triage Possible bug which hasn't been reproduced yet v3
Projects
None yet
Development

No branches or pull requests

1 participant