Tom Bevan

Hi @jdmeyer3 Thanks for raising the issue. There was a bug with the way patch was setting nil values on structs. This should be fixed in `v2.13.5`. Please could you...

Hey @jdmeyer3 Thanks for providing the additional test case! Unfortunately while that fix does not cause a panic, if you check it with your original example you will find that...

Hi @chbiel, thanks for raising the issue and sorry for the late response! There a few things to note here about the behaviour of `Diff` and the way it handles...

Hi @hwebb, thanks for raising the issue. I pretty much agree with what @hjr265 said. Directly supporting types from external libraries is outside the scope of this project as it...

Hey @amanenk, Sorry for the delay in getting back to you and thanks for raising the issue! This is a bit of a tricky one... When diffing two slices with...

Hey, I'm not massively familiar with your usecase and how apply/patch and reverse patch works, would you be able to provide an example of how it works? I'm very much...

Thanks for clarifying. That sounds like a very worthwhile feature and seems like a good fit for the library. If you need any assistance in the implementation, let me know!

Hey @ryjogo , not entirely sure I understand what you're trying to accomplish. If you are only after applying changes that add or update, then you could just iterate through...

Hey @nofik44 thanks for the contribution. Happy to merge this if you can remove the changes to the go mod file please?

Looks to be an issue with the template variable generated from the "new" build being diffed with the "actual" value stored from the last build. Given that the values field...