Which has led to a new wider hashing capability for the low level API. hashing makes it very easy to determine changes quickly, without having to run comparisons to discover changes, could really speed things up moving forward.
Design is more uniformed and standardized, patterns are bubbling up. I think we're ready to tackle the schema soon.
Signed-off-by: Dave Shanley <dave@quobix.com>
Everything will now calculate total changes and breaking changes as a convenience and aggregation mechanism.
Signed-off-by: Dave Shanley <dave@quobix.com>
Still quite early in the pattern finding process, needs another sweep to cache and fetch more pre-calculated change counts.
Signed-off-by: Dave Shanley <dave@quobix.com>
tried to make some more generic patterns, but I think it's about as thin as it can be now, some boilerplate will be required.
Signed-off-by: Dave Shanley <dave@quobix.com>
They are not useful and will create a lot of noise, The context will always be available, but changes in context will not result in a recorded change.
Signed-off-by: Dave Shanley <dave@quobix.com>
The designs and patterns are set, the way forward for low-level models is clear. Documentation and cleanliness will now be a side by side process as the rest is built out.
Signed-off-by: Dave Shanley <dave@quobix.com>
