Utility class for fetch functions used in @nestia/sdk.
PlainFetcher is a utility class designed for SDK functions generated by
@nestia/sdk, interacting with the remote
HTTP server API. In other words, this is a collection of dedicated fetch()
functions for @nestia/sdk.
For reference, PlainFetcher class does not encrypt or decrypt the body data
at all. It just delivers plain data without any post processing. If you've
defined a controller method through @EncryptedRoute or @EncryptedBody
decorator, then EncryptedFetcher class would be used instead.
contracts/common.md#principled-implementation The codecs preserve transformed bodies, while FetcherBase owns JSON, form and binary handling. Encrypted metadata is refused before transport. The shared pipeline removes caller Content-Type case-insensitively so multipart boundaries remain fetch-owned, normalizes only host/path separator boundaries, and classifies 200, 201 and the route's configured success status.
Evidence
contracts/common.md#clear-and-simple-design Two public operations that mirror EncryptedFetcher, with the encryption guard as their only own logic.
Evidence
contracts/common.md#prohibited-implementation-shortcuts The refusal is the contract with the generated SDK, which chooses EncryptedFetcher for encrypted routes; no route or header is special-cased.
Evidence
contracts/common.md#meaningful-documentation The namespace prose says when the generated SDK uses this fetcher and that it does no encryption.
Utility class for
fetchfunctions used in@nestia/sdk.PlainFetcheris a utility class designed for SDK functions generated by@nestia/sdk, interacting with the remote HTTP server API. In other words, this is a collection of dedicatedfetch()functions for@nestia/sdk.For reference,
PlainFetcherclass does not encrypt or decrypt the body data at all. It just delivers plain data without any post processing. If you've defined a controller method through@EncryptedRouteor@EncryptedBodydecorator, then EncryptedFetcher class would be used instead.Author
Jeongho Nam - https://github.com/samchon
Evidence
contracts/common.md#principled-implementation The codecs preserve transformed bodies, while FetcherBase owns JSON, form and binary handling. Encrypted metadata is refused before transport. The shared pipeline removes caller Content-Type case-insensitively so multipart boundaries remain fetch-owned, normalizes only host/path separator boundaries, and classifies 200, 201 and the route's configured success status.
Evidence
contracts/common.md#clear-and-simple-design Two public operations that mirror
EncryptedFetcher, with the encryption guard as their only own logic.Evidence
contracts/common.md#prohibited-implementation-shortcuts The refusal is the contract with the generated SDK, which chooses
EncryptedFetcherfor encrypted routes; no route or header is special-cased.Evidence
contracts/common.md#meaningful-documentation The namespace prose says when the generated SDK uses this fetcher and that it does no encryption.