1.106.2 (2022-02-27)
1.106.1 (2022-02-21)
1.106.0 (2022-02-21)
1.105.2 (2022-02-17)
1.105.1 (2022-02-14)
1.105.0 (2022-02-12)
1.104.1 (2022-02-12)
1.104.0 (2022-01-21)
1.103.0 (2022-01-20)
1.102.2 (2022-01-19)
1.102.1 (2022-01-19)
1.102.0 (2022-01-18)
1.101.0 (2022-01-15)
1.100.1 (2022-01-10)
1.100.0 (2022-01-09)
1.99.0 (2022-01-07)
1.98.0 (2022-01-06)
1.97.2 (2022-01-06)
1.97.1 (2022-01-05)
1.97.0 (2021-12-30)
1.96.1 (2021-12-28)
1.96.0 (2021-12-24)
1.95.1 (2021-12-23)
1.95.0 (2021-12-14)
1.94.0 (2021-12-14)
1.93.3 (2021-12-13)
1.93.2 (2021-12-09)
1.93.1 (2021-12-08)
1.93.0 (2021-12-08)
1.92.2 (2021-12-08)
1.92.1 (2021-12-02)
1.92.0 (2021-11-28)
1.91.0 (2021-11-27)
- use Long.fromValue instead of Long.fromString for improved robustness regarding already parsed objects (#405) (7bdc3ee)
1.90.1 (2021-11-27)
1.90.0 (2021-11-24)
1.89.0 (2021-11-24)
1.88.0 (2021-11-22)
1.87.1 (2021-11-21)
1.87.0 (2021-11-16)
1.86.0 (2021-11-15)
1.85.0 (2021-11-02)
1.84.0 (2021-11-02)
1.83.3 (2021-10-28)
1.83.2 (2021-10-26)
1.83.1 (2021-09-17)
1.83.0 (2021-09-12)
1.82.5 (2021-08-05)
1.82.4 (2021-08-04)
1.82.3 (2021-08-03)
1.82.2 (2021-07-11)
1.82.1 (2021-07-11)
1.82.0 (2021-06-28)
1.81.3 (2021-06-13)
1.81.2 (2021-06-13)
1.81.1 (2021-05-23)
1.81.0 (2021-05-23)
1.80.1 (2021-05-18)
1.80.0 (2021-05-09)
1.79.8 (2021-05-09)
1.79.7 (2021-04-27)
1.79.6 (2021-04-24)
1.79.5 (2021-04-24)
1.79.4 (2021-04-23)
1.79.3 (2021-04-16)
1.79.2 (2021-04-07)
1.79.1 (2021-04-04)
1.79.0 (2021-04-02)
1.78.1 (2021-04-02)
1.78.0 (2021-04-02)
- Fix bytes initialization. Fixes #237. (willclarktech and webmaster128)
- Better camelization for
FOO_BAR
tofooBar
- Add
message.$type
fields and a type register. See #254. (aikoven) - Don't output long initialization for only types. Fixes #247.
- Always initial long when
forceLong=long
. Fixes #247. (daw1012345)
- Fix
stringEnums
combined withoutputEncodeMethods
- Fix
@improbable-eng
imports to work with babel. (m!m)
- Fix compiler errors when strict is enabled. Fixes #235. (Graham)
- Revert the change in v1.70.0 that changed
useOptionals
handling of repeated fields.
Before this PR, useOptionals
was purely a type system tweak, and this PR introduced a
change to decoding semantics, so it needs to be re-introduced under a separate flag to
avoid being a breaking change.
- Add
constEnum
option to enableconst
enums. Fixes #230. (lxgreen)
- Update
useOptionals
to make repeated fields optional as well. Fixes #225. (i-dot)
- Actually fix #223.
- Allow setting
outputJsonMethods=true
while usingnestJs=true
. Fixes #223.
- Add
outputPartialMethods
. See #207. (mharsat)
- Allow
returnObservable=true
when not using grpc-web. See #220. (ardyfeb) - Fix
useDate=false
in encoding/JSON methods. See #211. (willclarktech) - Revert back to object spread instead of
Object.create
for primitive default values. Fixes #218.
- Fix
globalThis
compilation errors with messages calledError
- Don't put default values on the wire while encoding. Fixed #213. (webmaster128)
- Qualify
Object.create
withglobalThis
to avoid collisions with message names ofObject
. Fixes #216.
- Use
ts-proto-descriptors
package to read/write theprotoc
stdinCodeGeneratorRequest
and stdoutCodeGeneratorResponse
messages.
-
Use
Object.create
indecode
to create messages so thathasOwnProperty
will be false for fields that are using default values.In theory fields being default values is not supposed to be observable (on the wire at least), but protobuf itself specifically uses this for the
FieldDescriptorProto.oneofIndex
field.
- New
outputSchema
option to include the*.proto
schema/metadata in the generated output file (Vilsol)
- Fix
DeepPartial
imports when services and messages are in separate files
- Fix JSON parsing of long wrapper values when forceLong != long (jessebutterfield)
- Accidental duplicate publish.
- Fix import collisions for imported-only symbols (stezu)
- Fix missing
fromTimestamp
import in generated code, fixes #200 (jessebutterfield)
- Fix
google.protobuf.BytesValue
infromPartial
&fromJSON
(ebakoba)
- Fix typo for method names in service output (willclarktech)
- Fix
stringEnums=true
infromJSON
andfromPartial
output (mharsat)
- Re-publish to fix previous publish error.
- Allow setting
addGrpcMetadata=true
w/o using NestJS (#188)
- Add
exportCommonSymbols
flag (defaultstrue
) that, whenfalse
skipsexport
ing a few common symbols (i.e.DeepPartial
) that make it more likely for multiple generated files to be imported byimport * from ...
and not have import conflicts, i.e. for barrel imports.
- Tweak
atob
&btoa
utility methods to prefixBuffer
withglobalThis
to avoid issues in non-node envs. Fixes #77.
- Avoid import conflicts when an imported message name matches a locally-declared message name, see #36.
- Import
protobufjs/minimal
as a default import when usingesModuleInterop
- This should fix running in "type: module" ESM modules, see #181
- Add new
esModuleInterop
option to fixLong
imports for projects that useesModuleInterop: true
in theirtsconfig.json
.
- Fix
DeepPartial
when used withLong
s (willclarktech)
- Polyfill
globalThis
for Node v10 support (willclarktech)
- Handle
@deprecated
when there are no other comments (ShakedH)
- Messages and fields that are marked as
deprecated
in*.proto
files will have a@deprecated
marker included in their JSDoc output (ShakedH) - Upgraded to the latest ts-poet
- [grpc-web] Remove
import =
to support not using synthetic default imports
- [grpc-web] Fix code generation errors introduced in v1.40.0
- [grpc-web] Revert breaking change of
unaryTransport
/invokeTransport
- Now client constructors take
transport
&streamingTransport
, and streaming calls will usestreamingTransport
is set, and otherwise fallback ontransport
.
- Now client constructors take
- [grpc-web] Remove
rxjs
dependency unless streaming is actually used
- Add support for grpc-web streaming responses (PhilipMantrov)
- Add
unrecognizedEnum
option for disabling theUNRECOGNIZED
enum values (ShakedH)
- Fix
forceLong
behavior when using wrapper types (Graham) - Add
rpcDataLoaderOptions
(Felix Mo) - Add
useDate
option to disablejava.util.Date
mapping (Graham)- This is primarily useful for NestJS which can only encode the original
google.protobuf.Timestamp
type
- This is primarily useful for NestJS which can only encode the original
- Add
stringEnums
option (Bastian Eicher)- Note this is not supported in the binary
encode
/decode
methods yet
- Note this is not supported in the binary
- Avoid unnecessary
import =
usage (Graham)
- Add a
protobufPackage
exportedconst
for metadata
- Fix maps of enums (@ahmadj-levelbenefits)
- Fix proto3 optional support
- Fix
blob
s infromPartial
andtoJSON
- Automatically configure
protobuf.util.Long
when 64-bit numbers are used (fixes #78)
- Add support for the experimental proto3
optional
keyword
- Fix
oneof=unions
not decoding default values correctly (@philikon)
- Accept cross-call metadata args in the
GrpcWebImpl
constructor - Accept
DeepPartial
request types for grpc-web calls
- Fix
toJSON
with maps of messages (#124 by @mscolnick)
- Use
enum
keyword for modeling keywords again - Fix maps of
google.protobuf.Timestamp
s - Fix name conflicts when using
google.type.Date
- Fix maps of bytes in JSON
- Add initial support for grpc-web using the
@improbable-eng/grpc-web
runtime
- Extra release to ensure the build output is correct.
- Added a
addNestjsRestParameter=true
that adds a...rest: any
parameter to use NestJS decorators like@CurrentUser
(@ToonvanStrijp)
- Added a
oneof=properties
that generatesoneof
s as an Abstract Data Type (ADT) of each option (@philikon)
- Added a
useOptionals=true
option that makes non-scaler/oneof fields optional, i.e.message?: Message
instead ofmessage: Message | undefined
(@philikon)
- Messages no longer use a base prototype to get default values. (@cliedeman)
-
Added a
env=both
option and made that the defaultThis restores the pre-1.22.0 behavior that bytes are
Uint8Array
so that theBuffer
support is not a breaking change. Users have to opt-in withenv=node
.Also fixes a bug introduced in 1.22.0 that output an
as Buffer
without first checkingenv=node
.
-
Added a
env=node
/env=browser
option that defaults toenv=node
Currently
env=node
only changes the types ofbytes
fromUint8Array
toBuffer
, as a convenience for Node programming whereBuffer
(which is the defacto subclass ofUint8Array
) is more widely used (@dolsup)
- Drop drop falsey values in maps in
decode
andfromPartial
. Fixes #79. (@timostamm)
- Repeated fields cannot be optional, fixes #80 (@philikon)
- Use
globalThis.Error
instead ofglobal.Error
for browsers, fix for #70
- Fix NestJS decorator for only-stream-in / only-stream-out methods
- Allow
Message.decode
methods to take aUint8Array
(orBuffer
) directly instead of having to pass aReader
- Another fix for NestJS-related
PACKAGE_NAME
consts
- Fix for NestJS-related
PACKAGE_NAME
consts
- Support for NestJS streams
- Added support for generating NestJS friendly output (thanks Ian Gregson!)
- See the readme for new options
nestJs
,lowerCaseServiceMethods
,returnObservable
, etc.
- See the readme for new options