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
Feature: Markdown support as a Markdown-specific Gutenberg Block #9357
Commits on Apr 26, 2018
Commits on Apr 29, 2018
-
-
Added patterns to protect non-Markdown blocks
Added patterns that will attempt to preserve all Gutenberg non-Markdown blocks from the Markdown parser.
-
Remove the PlainText block wrapper
Remove the textarea wrapper to avoid rendering it as a textarea form element for the reader.
-
Reuse markdown content on Meta Box update
The idea here is to reuse the existing original Markdown, on the second post for Meta Boxes following a `Save Draft` event. This way when the markdown parser runs a second time it does not parse the rendered markup in `post_content` and overwrite the original Markdown in `post_content_filtered`.
-
-
Merge branch 'add/gutenberg-markdown-block' of https://github.com/nuz…
…zio/jetpack into add/gutenberg-markdown-block # Conflicts: # modules/markdown/assets/js/jetpack-markdown-block.jsx
Commits on May 1, 2018
-
-
-
-
-
-
-
-
-
-
-
so that Markdown formatting syntax is not processed within block-level HTML
-
-
Added filter call for Gutenberg edit post
apply filter is located in wp-content/plugins/gutenberg/lib/client-assets.php line 841
Commits on May 2, 2018
-
do this prior to attempting block registration.
-
Simplified textarea save format
Using a textarea preserves the newlines in the input field faithfully on the POST. These are caught by the `strip_gutenberg_text_area_wrapper` to remove the node for the user side and introduce additional newlines for proper formatting.
-