Skip to content

Plain JSON Schema semantics and explicit resolution for schema composition #123

Open

Description

@mindsocket

Summary

Follow-up to #121. Make schema composition behave like plain JSON Schema, and reduce the remaining implicit behaviour.

Proposal

  • Plain allOf and $ref semantics.
    • Drop the sibling-key overlay on $ref (src/schema/schema-refs.ts:55-82).
    • Drop the "later properties win" flattening of allOf (schema-refs.ts:157-229).
    • A shallow scan of the bundled schemas found no uses of either.
  • Explicit registry search paths instead of the _ prefix auto-load. Today, _-prefixed files auto-load as partials, but only from the bundled directory and the schema's own directory (docs/schemas.md:308-310). Schemas would instead resolve by $id through configured search paths.
  • Entity types arrive with imports. An imported schema's entity types join the importing schema's type union automatically, so composing schemas no longer hand-list every type in oneOf.

Relates

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions