Conversation
Several TOML snippets used a separate [project.markdown_extensions...] table header for each sibling extension, mirroring a YAML conversion rather than idiomatic TOML. Collapse these into a single parent table with inline table values, taking advantage of TOML 1.1's newlines in inline tables for the larger multi-key cases. Closes #104
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
1 participant
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.
Several TOML snippets used separate top-level tables for each sibling extension. This PR changes that, making use of new features of TOML 1.1.
The largest single change is in the default configuration.
We should probably also convert the bootstrap
zensical.toml.Some tidying up for line-length still needed as well as checking that nothing broke. Hence a draft PR for now.