@waffle8946 It’s really just the second PR, here’s the release note for that:
Copy for readability:
- Structure of the
functor
of some types has changed.functor
is an implementation detail and should not be relied upon. If you did rely on it let us know in this PR.lib.types.enum
: Previously thefunctor.payload
was the list of enum values directly. Now it is an attribute set containing the values in thevalues
attribute.lib.types.separatedString
: Previously thefunctor.payload
was the seperator directly. Now it is an attribute set containing the seperator in thesep
attribute.
If you used these internal fields for type merging before, you can do this instead:
mergeTypes = a: b: a.typeMerge b.functor;