Tags: webrpc/gen-javascript
Tags
fix: keep schema hash on by default, omit via -schemaHash=false v0.15.0 made schema hash emission opt-in (default off), a breaking change for consumers that rely on the hash and version constants. Restore the hash to on by default and make omission opt-out instead. - default (or -schemaHash): hash + version constants emitted, as before v0.15.0. - -schemaHash=false: omits the hash from the header comment and the version constants (WebRPCVersion, WebRPCSchemaVersion, WebRPCSchemaHash). The "Code generated by ... DO NOT EDIT." line stays. Regenerated _examples (hash restored).
feat: make schema hash and version constants opt-in via -schemaHash The schema hash in the file header comment and the WebRPCSchemaHash constant change on every schema edit, producing perpetual git merge conflicts in generated files. The version constants (WebRPCVersion, WebRPCSchemaVersion, WebRPCSchemaHash) are rarely consumed. Gate them behind a new -schemaHash target option (default false), flipping the previous always-on behavior: - default: header comment carries only the name and version (no hash), and no version constants are emitted. The "Code generated by ... DO NOT EDIT." line stays. - with -schemaHash: restores today's output exactly (hash in the header plus all three constants). Regenerated _examples to reflect the new default.
Update templates to [email protected] schema (#2) * README: Update options * Update to [email protected] * Fix types * Improve generated code * Switch webrpc to webrpc/webrpc#171 * Regenerate tests
PreviousNext