Releases: tatethurston/ProtoScript
v0.0.23
v0.0.22
What's Changed
- Fix Timestamp and Duration JSON serialization. Previously, when either seconds or nanos were 0, the Timestamp / Duration was omitted from the serialized json. Thanks @martynchamberlin!
Full Changelog: v0.0.21...v0.0.22
v0.0.21
v0.0.20
What's Changed
- Preserve protoscript import when well known types are imported by @tatethurston in #47
Full Changelog: https://github.com/tatethurston/ProtoScript/blob/main/CHANGELOG.md#v0020
v0.0.19
What's Changed
- JSON wireformat fixes by @tatethurston in #41
- initialize now accepts partial messages by @tatethurston in #45
Full Changelog: https://github.com/tatethurston/ProtoScript/blob/main/CHANGELOG.md#v0019
v0.0.18
v0.0.18
- Fix JSON deserialization of recursive (self referencing) messages.
- Fix generated TypeScript types for repeated recursive (self referencing) messages.
Full Changelog: v0.0.17...v0.0.18
v0.0.17
v0.0.17
- Omit
Uint8ArrayfromPartialDeeptype. This fixes a type error for TypeScript users that usebytes.
Full Changelog: v0.0.16...v0.0.17
v0.0.16
v0.0.16
encodemethods now accept partials for nested messages as well (PartialDeepinstead ofPartial). Previously, the types required that full messages were provided for any nested messages.
Buf users will need to update their buf.gen.yaml path:
buf.gen.yaml
version: v1
plugins:
- name: protoc-gen-protoscript
- path: ./node_modules/protoscript/compiler.js
+ path: ./node_modules/protoscript/dist/compiler.js
out: .
opt:
- language=typescript
strategy: allFull Changelog: v0.0.15...v0.0.16
v0.0.15
v0.0.15
This release includes the following bug fixes:
- Fix treeshaking for nested messages. Previously, there were cases where protobuf did not tree shake out of JSON only client usage. Thanks @noahseger!
- Fix camelcasing for fieldnames with multiple sequential underscores. Thanks @noahseger!
- Fix generated toInt helper when using aliased enums. Thanks @noahseger!
- Fix recursive message initialization. Previously, recursive messages, messages with fields that referenced themselves, would cause an infinite loop when initializing because protoscript eagerly instantiates message objects. Now the compiler detects cycles and will instead generate up until the cycle, and mark the recursive field as optional.
New Contributors
- @noahseger made their first contribution in #26
Full Changelog: v0.0.14...v0.0.15
v0.0.14
v0.0.14
-
Fix intermittent EAGAIN issue encountered when compiling protos
-
Use glob imports for generated messages instead of destructuring. This preserves tree shaking, but preserves module namespacing to disambiguate name collisions between protos. Previously, identically named messages in different modules could causes a name collision, eg:
// foo.proto message Foo {}
// bar.proto import "foo.proto"; message Foo {}
Would result in errors in the generated code. Now, this is namespaced and works correctly.
Full Changelog: v0.0.13...v0.0.14