Repository navigation
fix: add a playground sample to the config schema - #3
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.
Adds an
x-playgroundsample to the config schema, which the dprint.dev playground puts in the editor when it opens this plugin, like dprint/dprint-plugin-typescript#899. The only option isnewLineKind, so there are no code examples.The sample is a
.bzlfile that isn't formatted, and formats to: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, or the playground sample doesn't format or is already formatted, and sets the sample's extension tobzl.