The v3 model is wrong and out of sync with the spec. It's been corrected, so the v2 and v2 model for SecurityRequirement have been collapsed down into a base model., they are the same data structures. This has allowed me to delete the complexity of sharing two different models for the same structure, by unifying the model correctly. I am not sure why I decided to change the v3 model, oh well, its been corrected. Long live swagger!
Self induced pain on some of this by changing the design between v2 and v3 (not sure why split one into a slice and not the other). Too many herbs, oh well. Perhaps a refactor down the road will help. The v2 model is inaccurate, not the v3, so... well, who cares. Death to swagger!
A number of changes, glitches and updates were required across the models, some of the hashing functions will need re-working when hashing maps after testing higher level concepts.
This one was perhaps one of the more frustrating models. It's a simple design, checking maps of string arrays for accurate changes - but the combinations make it a bit of a challenge. I hope I've caught the variations correctly. Bloody swagger, the sooner you go away, the easier all of our lies will be.
Designs for handling multiple versions of objects have been set, seems clean and scalable. Generic functions for handling maps has been added also, which will cut down time moving forward.
Parameter dependencies mean we're back in the ball of yarn stage. Coverage is going to drop for a bit, until all the new hashing and interfaces are in place.
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>
