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
It is to me easier to expect two calenders to equal if they have the same components and values. #568 shows that some components or attributes use object identity when compared where value equality is expected. I open this issue to discuss this and wonder if we could transit to a unified approach to compare values. What would be the challenges?
What are your thoughts?
The text was updated successfully, but these errors were encountered:
I think that for a start, we could read in all calendar files that are there twice and compare the two. Some from niccokunzmann/x-wr-timezone#8 might also show which elements are not equal.
This is live in v5.0.11. Thanks for your contributions!
I will close this for now as it solves my use-cases. If any class escapes proper equality comparison, we should open another issue.
It is to me easier to expect two calenders to equal if they have the same components and values.
#568 shows that some components or attributes use object identity when compared where value equality is expected. I open this issue to discuss this and wonder if we could transit to a unified approach to compare values. What would be the challenges?
What are your thoughts?
The text was updated successfully, but these errors were encountered: