cratis-fundamentals-concept

Topics in the source

• Cratis domain concepts and event-source identities
• Verified product sources
• Choose the type
• Create a value concept
• Absence and sentinels
• Let a concept generate its own value
• Choosing a strategy
• When not to generate

Replace a primitive only when the domain gives it distinct meaning. Keep value concepts and Chronicle stream identities separate. Sources: | Package | Purpose | | --- | --- | | Cratis.Fundamentals | ConceptAs , IGeneratable , IGeneratableInContext , GenerationContext and GenerateValue | | Cratis.Chronicle | Cratis.Chronicle.Events.EventSourceId and EventSourceId | | @cratis/fundamentals | TypeScript ConceptAs , field, Guid, and JSON conversion | Reverify product sources before claiming support for another version. Derive a name, amount, code, number, or non-stream entity ID from ConceptAs . Derive an identity from EventSourceId only when that value is actually passed to Chronicle as the event-source/stream ID. Do not use ConceptAs for a Chronicle stream identity. Do not use EventSourceId merely because a value is called an ID. Do not wrap an enum. An enum already expresses a closed domain concept. Keep DTO-only transport values primitive unless the domain type belongs in the public contract. Both generic bases require an underlying type that implements IComparable. A value concept contains exactly one wrapped value. Do not add extra properties; Fundamentals converters assume the co

This is an excerpt. Refer to the complete source and its current requirements.