Skip to content

Describe collection names that follow Arc's naming policy on the JVM and TypeScript backends - #157

Merged
woksin merged 1 commit into
mainfrom
docs/19-camel-casing-naming
Sep 29, 2026
Merged

woksin merged 1 commit into
mainfrom
docs/19-camel-casing-naming

Conversation

@woksin

@woksin woksin commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

The camel-casing scenario told Kotlin, Java and TypeScript readers to work around a collection-name mismatch: Chronicle wrote projected read models to an unpluralized collection, and Arc read a pluralized one. That mismatch is fixed across the stack:

The Arc snippets this page tabs already show the new setup. This updates the prose to match:

  • Kotlin and Java: collection names need no configuration. The section says which Chronicle.Kotlin version is required, how to choose other names (an Arc NamingPolicy bean, or a Chronicle ReadModelNamingPolicy bean), and what an app that declares its own ChronicleOptions must do. The pluralizeReadModelNames = false workaround and the Update managed AI corpus to v2.0.8 #105 link are gone.
  • TypeScript: collection names follow Arc for read models listed in withMongoDB's readModels; others keep their identifier. The section gives the required @cratis/chronicle version and the own-client case. It also says withMongoDB's database must match the event store name. The collectionName: type => type.name workaround, the .containerName() caveat and the Revise the capstone and vertical-slice pages for every backend #149 link are gone. It no longer says the TypeScript client has no naming policy option.

Checked locally, with the siblings taken from origin/main:

  • node --test scripts/*.test.mjs, npm run lint:docs and npm run audit:variant-docs pass.
  • lint-prose reports only the page's existing "camelCase" spelling flags.

Review: same-provider (Anthropic-only); I wrote the change and checked it against the merged Arc snippets.

Refs #19

@woksin woksin self-assigned this Sep 29, 2026
@woksin
woksin merged commit f867e72 into main Sep 29, 2026
3 checks passed
@woksin
woksin deleted the docs/19-camel-casing-naming branch September 29, 2026 22:45
@woksin woksin mentioned this pull request Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant