Dave Shanley
e1e91d0682
Bumping coverage
...
checking all the corners for cobwebs
2022-11-20 14:30:50 -05:00
Dave Shanley
26d3535e75
Working through what-changed fixes and tuneups.
...
more testing is required, however things feel quite reasonable and rounded. All changes correctly detected in a spec so far.
2022-11-20 14:30:50 -05:00
Dave Shanley
97a03315d6
Smashing bugs in models by validating changes.
...
Who would have thought the what-changed tool would be the key to ensuring accuracy on the models.
2022-11-20 14:30:50 -05:00
Dave Shanley
22ca3ced63
discovered a bug in content changes
...
Switching machines, I can’t use this laptop for any real work.
Signed-off-by: Dave Shanley <dshanley@splunk.com >
2022-11-20 14:30:50 -05:00
Dave Shanley
a8a8b482d8
Hardening model whilst testing what-changed feature.
...
Checking and sampling, and fixing bugs while working through testing.
Signed-off-by: Dave Shanley <dshanley@splunk.com >
2022-11-18 14:11:19 -05:00
Dave Shanley
9d8d6e36ea
what-changed operational
...
the code is working, the tests are passing. There is a lot more to check, but it's a good time to bring the feature into main.
2022-11-18 11:00:34 -05:00
Dave Shanley
b510be3563
what-changed code in place.
...
Let the explosions begin!
2022-11-18 11:00:34 -05:00
Dave Shanley
65fa21be86
Continued pattern building, added info changes
...
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 >
2022-10-03 09:46:12 -04:00
Dave Shanley
cd68570278
Fleshing out what-changed functionality.
...
Starting at the bottom again with low levels and sketching out how to consume it.
2022-09-28 11:41:59 -04:00