Enable stricter Markdown parsing and fix surfaced issues#13611
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Collaborator
|
Staged preview of the updated docs.flutter.dev site (updated for commit 847369e): https://flutter-docs-prod--docs-pr13611-feat-stricter-markdown-0voarqyj.web.app |
Collaborator
|
Staged preview of the updated flutter.dev site (updated for commit 847369e): https://flutter-dev-230821--www-pr13611-feat-stricter-markdown-pasf6qt4.web.app |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This enables stricter parsing of inline Markdown, failing the build and reporting an error if there are unclosed HTML elements, which would have potentially caused misformatting of the page contents. It then fixes the issues surfaced by the stricter parsing.
Resolves #12045