Releases: palantir/conjure-go
Releases · palantir/conjure-go
v5.0.3
v5.0.2
v5.0.1
v5.0.0
Type | Description | Link |
---|---|---|
Improvement | Generated error types now implement the wparams.ParamStorer interface. This ensures any downstream consumers of the error (e.g., witchcraft-go-logging) will automatically do the right thing with the params. |
#114 |
Improvement | Each generated conjure error type is registered with CGR's error registry via an init() function, allowing unmarshal errors into the generated error struct types. This unblocks returning real conjure errors. One init() function will be added to register all error types in a given package. |
#115 |
Break | Bump conjure-go-runtime dependency to v2. This picks up improvements to decoding conjure error types. | #116 |
Break | Generated servers emit conjure errors, allowing them to be deserialized by conjure-go-runtime clients | #117 |
Break | Conjure generated servers now use the github.com/palantir/conjure-go-runtime/conjure-go-server library for request handling. This change correctly handles conjure error status codes and prioritizes them over any legacy error code. It also writes non-json-marshalable errors as plaintext with the correct headers. |
#118 |
Break | Update module to v5 | #119 |
v4.3.1
v4.3.0
Type | Description | Link |
---|---|---|
Improvement | Uses the latest Conjure API definitions and updates generation file code and IR filename to include the version. | #106 |
Fix | Ensure that imports for endpoint definitions are processed and added before generating server code so that import paths for endpoint objects are correct. |
#107 |
v4.2.2
v4.2.1
v4.2.0
Type | Description | Link |
---|---|---|
Fix | Use palantir/go-ptimports instead of palantir/checks Use the non-deprecated project to perform formatting. This change also modifies the parameters provided to the formatter, which changes the imports in generated code by no longer separating project imports into their own block. |
#100 |
Feature | Add module definition | #101 |
Fix | Ensure import paths are correct in modules If the generated code is within a module, ensure that the import paths are relative to the module root. Fixes #98 |
#99 |