You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👋🏻 hey there
I'm using this library as it has been the most consistent way to compare structs that I've found so far, thanks!
one feature that I'm missing is the option to ignore unexported fields from being compared and marked as differences, I know I can strip them by marshal/unmarshal but if that functionality would be provided by the library itself that would be amazing 🙂
I'm ok with implementing it myself and submitting a pr!
I would like to know
is this something you're ok with adding?
is there some limitation that I could hit while adding this feature?
any hints where I should start from?
I haven't checked the codebase yet, that's why I'm asking this 😅
The text was updated successfully, but these errors were encountered:
hmm... I guess that's the way to handle it, right?
I'd be ok with either documenting it as example or adding an explicit option for this
imo that would make it more obvious
while I was aware of the diff:"-" struct tag I don't want to keep track of this and make sure to add it every time we add an unexported field; the filter works alright though, so I'm happy with that
I still think that maybe documenting this would be nice, as it didn't struck me as something obvious on the first place
but up to you 🙂 feel free to close this issue if there is nothing else to discuss here
👋🏻 hey there
I'm using this library as it has been the most consistent way to compare structs that I've found so far, thanks!
one feature that I'm missing is the option to ignore unexported fields from being compared and marked as differences, I know I can strip them by marshal/unmarshal but if that functionality would be provided by the library itself that would be amazing 🙂
I'm ok with implementing it myself and submitting a pr!
I would like to know
I haven't checked the codebase yet, that's why I'm asking this 😅
The text was updated successfully, but these errors were encountered: