Repository navigation
fix: update dprint-core to 0.75.2 and add code examples to the config schema - #33
Merged
Merged
Conversation
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
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.
Updates dprint-core to 0.75.2, which has printer performance fixes and no API changes.
Also improves the configuration documentation that dprint.dev renders from
schema.json, like dprint/dprint-plugin-typescript#898 and #899:x-playground: unformatted TypeScript that the dprint.dev playground starts with when this plugin is selected.x-exampleon 16 properties: input code that's formatted with each of the property's values. The repo'sschema.jsononly has the inputs. The outputs are generated with the built plugin when the schema is published.x-sections: the properties grouped into seven sections (General, Semicolons/commas/quotes, Line breaks and spaces, HTML and JSX, Sorting, Embedded code and comments, Languages).htmlWhitespaceSensitivity, which was anenum, the boolean form ofsortPackageJson, and thesortImports.customGroupsselectors and modifiers), and uses code spans in descriptions.integerwith a minimum and maximum forindentWidthandlineWidth, and says which values Oxc supports.The new "Generate config schema" CI step runs the
publish-schematask from dprint/automation on the built wasm plugin, before the schema is uploaded to a release. It fails when the plugin has a diagnostic for a property's default, an example formats the same with every value, a top level property isn't in exactly one section, or the playground sample doesn't format or is already formatted. Deno is now set up on every run instead of only on tags, since the step needs it.To see the generated schema locally: