How to get the html string?

[langsz]

Is there any api in mildown to get the html string?

[Saul-Mirone]

Why not just use document.querySelector('.milkdown').outerHTML?

[Saul-Mirone]

You can also write a simple action which will be provided officially in v6.0:

/* Copyright 2021, Milkdown by Mirone. */
import { Ctx, editorViewCtx, schemaCtx } from '@milkdown/core';
import { DOMSerializer } from '@milkdown/prose';

export const getHTML = () => (ctx: Ctx) => {
    const div = document.createElement('div');
    const schema = ctx.get(schemaCtx);
    const view = ctx.get(editorViewCtx);
    const fragment = DOMSerializer.fromSchema(schema).serializeFragment(view.state.doc.content);

    div.appendChild(fragment);

    return div.innerHTML;
};

const html = editor.action(getHTML());

[langsz]

Get it

[seeARMS]

Is this now officially provided in the v6 release? I couldn't find any method involving getHTML.

EDIT: Nevermind: https://github.com/Saul-Mirone/milkdown/blob/5ab806086322e23f851749c2c10b8976e165b896/packages/utils/src/macro/get-html.ts

[langsz]

You can also write a simple action which will be provided officially in v6.0:

/* Copyright 2021, Milkdown by Mirone. */
import { Ctx, editorViewCtx, schemaCtx } from '@milkdown/core';
import { DOMSerializer } from '@milkdown/prose';

export const getHTML = () => (ctx: Ctx) => {
    const div = document.createElement('div');
    const schema = ctx.get(schemaCtx);
    const view = ctx.get(editorViewCtx);
    const fragment = DOMSerializer.fromSchema(schema).serializeFragment(view.state.doc.content);

    div.appendChild(fragment);

    return div.innerHTML;
};

const html = editor.action(getHTML());

@Saul-Mirone I use the code to get the html, but there is some different with the html in the editor.
for example,

when checked the html elements,

Do you have any method make them in the same?

[Saul-Mirone]

Because some of the plugins are rendered by nodeviews in prosemirror. And when DOM seriailizer parse them, they'll rendered by toDOM instead of nodeViews. I'm still thinking a good solution about this.

[langsz]

Because some of the plugins are rendered by nodeviews in prosemirror. And when DOM seriailizer parse them, they'll rendered by toDOM instead of nodeViews. I'm still thinking a good solution about this.

Looking forware to your good solution.Thank you