Repository navigation
chore(release): 0.4.4 - #4
Merged
Merged
Conversation
pyo.jsonc is JSON with comments and trailing commas, with camelCase keys that match the API (autoRollback, serveAs, build.dockerfilePath). pyo link writes a new file with "$schema" and "service", and changes only "service" in an existing one, keeping its comments and layout. Unknown settings still fail, naming the setting and the file. The JSON Schema comes from the config types. A test checks that pyo-docs/schema/pyo.json matches it, and PYO_WRITE_SCHEMA=1 rewrites it. A pyo.toml found before any pyo.jsonc stops with one line that points to pyo link.
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.
Pyo 0.4.4: everything on dev since 0.4.3, pyo.jsonc as the CLI's project file with its JSON Schema, and the version bump.