Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
32 KiB
@atproto/lex-client
0.0.20
Patch Changes
-
#4816
61e75afThanks @matthieusieben! - On NodeJS, improve error reporting by unwrapping undici errors -
Updated dependencies [
26d793a,952354c]:- @atproto/lex-schema@0.0.19
- @atproto/lex-json@0.0.16
0.0.19
Patch Changes
-
#4839
b6b231fThanks @matthieusieben! - Fix typing ofdeleteoptions to omitbodyinstead ofparams. -
#4828
c62651dThanks @matthieusieben! - Accept legacy blob references in non-strict mode. Legacy blob references (objects withcidandmimeTypeproperties) are now accepted whenstrict: false, which is the default behavior whenstrictResponseProcessingis disabled on the Client.BREAKING: The
allowLegacyoption has been removed from the blob schema builder, and legacy blobs are now handled automatically based on the strictness mode: in strict mode they are rejected, and in non-strict mode they are accepted. Consumers should stop passingallowLegacyand rely on strictness configuration instead. Likewise, CLI consumers should stop using the removed--allowLegacyBlobsflag and use the default strict/non-strict behavior. -
#4835
f6f100cThanks @matthieusieben! - UselexParseJsonBytesto convert binary data directly into lex value -
Updated dependencies [
c62651d,f6f100c,c62651d,c62651d,f6f100c]:- @atproto/lex-data@0.0.15
- @atproto/lex-schema@0.0.18
- @atproto/lex-json@0.0.15
0.0.18
Patch Changes
-
#4779
527f5d4Thanks @matthieusieben! - Improve handling of XRPC response errors by always usingXrpcResponseErrorerrors when upstream server responds with an error status code. Before,XrpcResponseErrorwould only be used if the upstream server responded with a valid XRPC payload (json witherrorfield). Any other response payload (e.g. non-json, invalid "error" payload) would be treated as the upstream server not being able to output a valid XRPC response, and would throwXrpcUpstreamErrorinstead. This change allows to better reflect upstream server errors to downstream services (eg. return a 429 if the upstream server responds with a 429 status code, instead of a 502, even if the response payload is not a valid XRPC error payload).XrpcUpstreamErrorwas removed and replaced withXrpcInvalidResponseErrorto better reflect the intent to those errors (invalid status code, non-json, or invalid payload).XrpcResponseValidationErroris a special case ofXrpcInvalidResponseErrorthat is thrown when the response does not conform to the expected XRPC output schema. -
#4788
a99dd58Thanks @matthieusieben! - Allow XRPC endpoints with nooutputspecified in their schema to output anything. -
Updated dependencies [
527f5d4,c4df84c,527f5d4,e5e5bcf,ac6bd18,c5c6c7d]:- @atproto/lex-schema@0.0.17
0.0.17
Patch Changes
-
#4761
6a88461Thanks @matthieusieben! - FixXrpcResponse.payloadto be typed as the schema's parse "Output" -
#4761
6a88461Thanks @matthieusieben! - Allow defining request and response processing defaults on theClientinstance -
#4773
df8328cThanks @matthieusieben! - RenameXrpcParamsOptionsasXrpcRequestParamsOptions -
#4761
6a88461Thanks @matthieusieben! - Add ability to process invalid Lexicon Data responses (instead of rejecting them as invalid) -
#4761
6a88461Thanks @matthieusieben! - Allow using a dynamic non-strict validation mode -
Updated dependencies [
6a88461,6a88461]:- @atproto/lex-schema@0.0.16
- @atproto/lex-data@0.0.14
- @atproto/lex-json@0.0.14
0.0.16
Patch Changes
-
#4714
5a2f884Thanks @matthieusieben! - Create a specific error class for wrapping unexpected error returned by thefetchHandler. This allows to better distinguish unexpected internal server errors (due to implementation encountering an unexpected case) from potentially transient errors that occur when performing network HTTP requests. -
Updated dependencies [
3dc3791,3dc3791,3dc3791,3dc3791,112b159,3dc3791,3dc3791]:- @atproto/lex-schema@0.0.15
0.0.15
Patch Changes
-
#4688
52834abThanks @matthieusieben! - Update error management to be more aligned with the way errors work in@atproto/xrpcand@atproto/xrpc-server -
#4688
52834abThanks @matthieusieben! - Add dedicatedXrpcInvalidResponseErrorerror for responses that don't match the schema -
#4688
52834abThanks @matthieusieben! - RenamematchesSchematomatchesSchemaErrorsto make it more explicit what is being matched when called on an XRPC "result" (that could either represent a success or failure) -
Updated dependencies [
52834ab,f7c2610,52834ab,52834ab,52834ab,52834ab,52834ab]:- @atproto/lex-schema@0.0.14
- @atproto/lex-data@0.0.13
- @atproto/lex-json@0.0.13
0.0.14
Patch Changes
- #4672
38852f0Thanks @matthieusieben! - Allow callingxrpcandxrpcSafefunctions with a service URL
0.0.13
Patch Changes
- Updated dependencies [
39dea03,ea5df64,ea5df64,39dea03,39dea03,ea5df64,39dea03,ea5df64,ea5df64,ea5df64,ea5df64,ea5df64,ea5df64,ea5df64,ea5df64]:- @atproto/lex-schema@0.0.13
- @atproto/lex-data@0.0.12
- @atproto/lex-json@0.0.12
0.0.12
Patch Changes
-
#4601
ed61c62Thanks @matthieusieben! - Add missing exports -
#4601
ed61c62Thanks @matthieusieben! - Fixexportsfield in package.json -
#4601
ed61c62Thanks @matthieusieben! - Add JSDoc -
#4601
ed61c62Thanks @matthieusieben! - Add JSDoc toClientclass properties and methods -
Updated dependencies [
7b9a98a,7b9a98a,ed61c62,ed61c62,7b9a98a,7b9a98a,ed61c62]:- @atproto/lex-schema@0.0.12
- @atproto/lex-json@0.0.11
- @atproto/lex-data@0.0.11
0.0.11
Patch Changes
-
#4589
369bb02Thanks @matthieusieben! - Add ability to set defaultheaderswhen creating XRPC agent -
#4589
369bb02Thanks @matthieusieben! - Improve typing of error responses -
#4589
369bb02Thanks @matthieusieben! - Allow omittingrkeyfor record definition usinanyas record key -
Updated dependencies [
369bb02]:- @atproto/lex-data@0.0.10
- @atproto/lex-json@0.0.10
- @atproto/lex-schema@0.0.11
0.0.10
Patch Changes
-
#4562
7310b97Thanks @matthieusieben! - RenameLexRpcFailuretoXrpcFailure,LexRpcOptionstoXrpcOptions,LexRpcResponsetoXrpcResponse,LexRpcResponseBodytoXrpcResponseBody -
#4562
7310b97Thanks @matthieusieben! - Remove dependency onURLSearchParams.sizewhen building XRPC request query string -
#4562
7310b97Thanks @matthieusieben! - RenamePayloadtoXrpcPayload -
Updated dependencies [
99963d0,7310b97,7310b97,7310b97,7310b97,7310b97,aaedafc,7310b97,7310b97,99963d0,7310b97,7310b97,99963d0,7310b97,99963d0,7310b97,7310b97]:- @atproto/lex-schema@0.0.10
- @atproto/lex-json@0.0.9
- @atproto/lex-data@0.0.9
0.0.9
Patch Changes
- Updated dependencies [
dfd4bee,dfd4bee,dfd4bee,dfd4bee]:- @atproto/lex-data@0.0.8
- @atproto/lex-json@0.0.8
- @atproto/lex-schema@0.0.9
0.0.8
Patch Changes
- Updated dependencies [
d78484f,d78484f,d78484f,d78484f,d78484f]:- @atproto/lex-data@0.0.7
- @atproto/lex-schema@0.0.8
- @atproto/lex-json@0.0.7
0.0.7
Patch Changes
-
#4501
2f78893Thanks @matthieusieben! - breaking: Use a record type (com.example.record.Main) instead of a record schema type (typeof com.example.record.$defs.main) as the generic parameter forListRecord. -
Updated dependencies [
2f78893,2f78893,2f78893,2f78893]:- @atproto/lex-data@0.0.6
- @atproto/lex-schema@0.0.7
- @atproto/lex-json@0.0.6
0.0.6
Patch Changes
-
#4443
9af7a2dThanks @matthieusieben! - ReworkXrpcErrorto extendLexErrorfrom@atproto/data -
#4443
9af7a2dThanks @matthieusieben! - ExposeasXrpcFailureutility -
#4443
9af7a2dThanks @matthieusieben! -buildAgentcan now be given anAgentas input (and will act as identity in that case) -
Updated dependencies [
9af7a2d,9af7a2d,9af7a2d,9af7a2d,9af7a2d,9af7a2d,9af7a2d,9af7a2d,9af7a2d]:- @atproto/lex-schema@0.0.6
- @atproto/lex-data@0.0.5
- @atproto/lex-json@0.0.5
0.0.5
Patch Changes
-
#4457
e6b6107Thanks @matthieusieben! - Complete rework of the error mechanics -
#4457
e6b6107Thanks @matthieusieben! - Add support foruploadBlobandgetBlobmethods -
#4457
e6b6107Thanks @matthieusieben! - Validate records whenvalidateRequestis set when callingcreateandputmethods. -
#4457
e6b6107Thanks @matthieusieben! - ExportFetchHandleras a distinct type -
#4457
e6b6107Thanks @matthieusieben! - No longer validate records whenvalidateoption is set increate()method. UsevalidateRequestoption for that purpose. -
#4457
e6b6107Thanks @matthieusieben! - RenameXrpcFailureerror name field toerrorfor consistency with XRPC error payloads -
#4457
e6b6107Thanks @matthieusieben! - Allow specifying request content-type through theencodingoption -
#4457
e6b6107Thanks @matthieusieben! - Improve handling of binary payloads -
#4457
e6b6107Thanks @matthieusieben! - RemovecreateRecordsSafe,deleteRecordsSafe,getRecordsSafeandputRecordsSafemethods -
Updated dependencies [
e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107,e6b6107]:- @atproto/lex-data@0.0.4
- @atproto/lex-schema@0.0.5
- @atproto/lex-json@0.0.4
0.0.4
Patch Changes
- Updated dependencies [
693784c]:- @atproto/lex-data@0.0.3
- @atproto/lex-json@0.0.3
- @atproto/lex-schema@0.0.4
0.0.3
Patch Changes
-
#4390
1d445afThanks @matthieusieben! - Rework object validation logic to work withoutoptionsargument -
#4405
2d13d05Thanks @matthieusieben! - Allow.call()argument "params" to beundefinedwhen all params are optional -
#4390
1d445afThanks @matthieusieben! - Replace use ofCIDwithCid -
#4389
bcae2b7Thanks @matthieusieben! - Use string formats from@atproto/syntax -
#4390
1d445afThanks @matthieusieben! - Rename schema methodsvalidate,checkandmaybetosafeParse,matchesandifMatchesrespectively. -
#4397
688f9d6Thanks @matthieusieben! - AddCHANGELOG.mdto npm package -
Updated dependencies [
1d445af,1d445af,1d445af,1d445af,1d445af,1d445af,a487ab8,a487ab8,1d445af,1d445af,a487ab8,a487ab8,1d445af,1d445af,bcae2b7,bcae2b7,1d445af,a487ab8,1d445af,9f87ff3,1d445af,688f9d6,1d445af]:- @atproto/lex-schema@0.0.3
- @atproto/lex-data@0.0.2
- @atproto/lex-json@0.0.2
0.0.2
Patch Changes
- Updated dependencies [
23c271f]:- @atproto/lex-schema@0.0.2
0.0.1
Patch Changes
-
#4371
46550d6Thanks @matthieusieben! - Release -
Updated dependencies [
46550d6]:- @atproto/lex-data@0.0.1
- @atproto/lex-json@0.0.1
- @atproto/lex-schema@0.0.1