docs: README accuracy sweep (schema field names, keystore path, versioning)#35
Merged
Merged
Conversation
…e path, versioning note)
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Launch-eve docs-vs-code accuracy sweep. Sibling PRs land at the same time on ligate-chain, ligate-js, ligate-api, ligate-explorer, ligate-marketing.
What changed
register-schemaJSON example field names corrected againstsrc/register_schema.rs:73-82:fee_routing_address→fee_routing_addr,payload_spec_hash→payload_shape_hash. Partners copy-pasting the README example were getting serde errors on unknown fields.ProjectDirs::from("io", "ligate", "cli")resolves to$XDG_DATA_HOME/cli/keys(thedirectoriescrate drops the org qualifier on Linux). README previously said$XDG_DATA_HOME/ligate/keys.v0.1.0-devnettov0.1.2-devnet.publish = falsenote alongside the SDK-pin-blocked crates.io reason.ligate node startis still deferred" rephrased to "not in scope for v0".ligate-chain#374(the convention shift to plain semver; next CLI release drops-devnet).Test plan