We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This provides a few benefits:
slate-hyperscript
Here's a potential API. The naming will almost surely change as I don't like it right now.
const structure = { blocks: { paragraph: "paragraph" }, marks: { bold: "bold" } } const { editor, html } = SlateTest({ plugins: Code() }, { structure }); const value = html` <paragraph> Some sample <bold>text</bold> </paragraph> `
A few open questions:
SlateTest
html
The text was updated successfully, but these errors were encountered:
Added https://github.com/ConvertKit/slate-plugins/tree/master/packages/slate-htm to potentially make this happen.
Sorry, something went wrong.
After writing many tests for Slate code here and in other repositories, I'm convinced this is the way to go now.
No branches or pull requests
This provides a few benefits:
slate-hyperscript
directlyHere's a potential API. The naming will almost surely change as I don't like it right now.
A few open questions:
SlateTest
function? In other words, should it be a separate import?html
name could be confusing, but it does automatically get you syntax highlighting depending on your editor setup.The text was updated successfully, but these errors were encountered: