Closed apelisse closed 1 year ago
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: apelisse
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/hold
I'm trying a new test with pruning fields that are removed by appliers and this doesn't work, looking into this.
/hold cancel
Thought about this further, I think it's fine, unless I forgot the use-case I had in mind ...
LGTM from me. I think you mentioned you wanted @jpbetz input so will defer tag
@alexzielenski: Closed this PR.
@alexzielenski: Reopened this PR.
whoops. brain misfire
/lgtm
Continuation of #247.
This uses the pattern that I've generally used to solve the problem, which is to not try to be too smart about duplicate entries, and just record the path element for the whole thing, rather than try to track all the fields within. It's not super relevant because no one should ever be able to apply duplicates, so they wouldn't really have conflicts with sub-fields anyway, we've decided that they should have a conflict with the idea of "duplicates" (de-duplicating is a conflict).
/assign @alexzielenski