Repository navigation
Describe collection names that follow Arc's naming policy on the JVM and TypeScript backends - #157
Merged
Merged
Conversation
…and TypeScript backends
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
@cratis/chronicle6.29.0 (Add an opt-in read model naming policy for container names Chronicle.TypeScript#152) add a read-model naming policy for container names.The Arc snippets this page tabs already show the new setup. This updates the prose to match:
NamingPolicybean, or a ChronicleReadModelNamingPolicybean), and what an app that declares its ownChronicleOptionsmust do. ThepluralizeReadModelNames = falseworkaround and the Update managed AI corpus to v2.0.8 #105 link are gone.withMongoDB'sreadModels; others keep their identifier. The section gives the required@cratis/chronicleversion and the own-clientcase. It also sayswithMongoDB'sdatabasemust match the event store name. ThecollectionName: type => type.nameworkaround, 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:docsandnpm run audit:variant-docspass.lint-prosereports 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