Skip to content

docs(core): document jsonOptions server option and per-service form#35

Open
intech wants to merge 1 commit into
mainfrom
feature/core-json-options
Open

docs(core): document jsonOptions server option and per-service form#35
intech wants to merge 1 commit into
mainfrom
feature/core-json-options

Conversation

@intech

@intech intech commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Documents the new server-level jsonOptions option on createServer() in the @connectum/core package guide, alongside the per-service form.

jsonOptions controls Connect's JSON serialization server-wide. The most common use is alwaysEmitImplicit: true, which includes fields with implicit presence (proto3 scalar 0, empty string/list, enum default) in JSON responses instead of omitting them. Because it is applied at the adapter level, it also covers framework-registered protocol services (healthcheck, reflection).

The guide also documents the per-service alternative via the third argument of router.service(), and notes the protobuf-es v2 field name (alwaysEmitImplicit, not the v1 emitDefaultValues).

Changes

  • en/packages/core.md: add the jsonOptions row to the CreateServerOptions table and a new "JSON serialization" subsection with examples.

Related

Documents the option added in Connectum-Framework/connectum#128.

🤖 Generated with Claude Code

Document the new `jsonOptions` option on `createServer()` for controlling
Connect JSON serialization server-wide (e.g. `alwaysEmitImplicit: true`),
plus the per-service `router.service()` form. Note the protobuf-es v2
field name (`alwaysEmitImplicit`, not the v1 `emitDefaultValues`).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added the type:docs Documentation: guides, README, JSDoc label Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type:docs Documentation: guides, README, JSDoc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant