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

Markdown to Lexical Example does not work #9813

Closed
cgilly2fast opened this issue Dec 8, 2024 · 2 comments
Closed

Markdown to Lexical Example does not work #9813

cgilly2fast opened this issue Dec 8, 2024 · 2 comments

Comments

@cgilly2fast
Copy link

Describe the Bug

Following document instructions on converting markdown to lexical does not work, follow you own example code exactly:

import {
  getEnabledNodes,
  sanitizeServerEditorConfig,
  defaultEditorConfig,
  $convertFromMarkdownString,
} from '@payloadcms/richtext-lexical'
import { createHeadlessEditor } from '@payloadcms/richtext-lexical/lexical/headless'
import configPromise from '@payload-config'

const config = await configPromise

  const sanitizedConfig = await sanitizeServerEditorConfig(defaultEditorConfig, config)

  const headlessEditor = createHeadlessEditor({
    nodes: getEnabledNodes({
      editorConfig: sanitizedConfig,
    }),
  })

const markdown = `# Hello World`

  headlessEditor.update(
    () => {
      $convertFromMarkdownString(markdown, sanitizedConfig.features.markdownTransformers)
    },
    { discrete: true },
  )

  const editorJSON = headlessEditor.getEditorState().toJSON()```

Issue is from $convertFromMarkdownString
Possibly line 54 from the source code:
https://github.com/payloadcms/payload/blob/main/packages/richtext-lexical/src/packages/%40lexical/markdown/MarkdownImport.ts

### Link to the code that reproduces this issue

https://see-below.com

### Reproduction Steps

See above

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

area: core

### Environment Info

```text
payload: 3.5.0
Next 15.0.4
"@payloadcms/richtext-lexical": "^3.5.0",
"lexical": "^0.20.0",
@cgilly2fast cgilly2fast added status: needs-triage Possible bug which hasn't been reproduced yet validate-reproduction labels Dec 8, 2024
Copy link
Contributor

github-actions bot commented Dec 8, 2024

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

@github-actions github-actions bot removed the status: needs-triage Possible bug which hasn't been reproduced yet label Dec 8, 2024
Copy link
Contributor

github-actions bot commented Dec 9, 2024

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant