Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distinguish Inputs, Assignments and Constraints #182

Merged

Conversation

DavePearce
Copy link
Collaborator

This refactors the notion of a Schema to specifically split components into: input columns, assignments and constraints. In addition, there are also property assertions (but these remain largely unused at this stage).

This splits up the existing package `table` into two packages, `trace`
and `schema`.  The goal here is just to reduce the amount of stuff in
the `schema` package and to provide a clear separation of concerns.
This puts through an extensive refactoring of a `Schema`.  Specifically,
a schema is made up of three components: _input columns_, _assignments_
and _constraints_.  To facilitate this, an `iterator` framework has been
developed to simplify the grouping of things together.
@DavePearce DavePearce linked an issue Jun 24, 2024 that may be closed by this pull request
@DavePearce DavePearce merged commit 721e3bc into main Jun 24, 2024
2 checks passed
@DavePearce DavePearce deleted the 178-distinguishing-between-inputs-assignments-and-constraints branch June 24, 2024 23:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Distinguishing between Inputs, Assignments and Constraints
1 participant