@dribbens @jmikrut I am experiencing another breaking type change that wasn't explicitly documented/called out in the release notes when updating from 1.6.24 -> 1.6.32. The group field seems to be changing from being potentially undefined to being required in the types...
See our previous discussion about this type of thing here:https://github.com/payloadcms/payload/commit/657aa65e993d13e9a294456b73adcd57f20d7c87
Are there plans to develop a better way of calling out breaking type changes like this?
The question I would like answered in this particular instance is when this changed?
Hey @TheDunco - yes, this change in specific is what led us to want to embracetrue
i talked a bit about this in my blog post here:
that change caused us ourselves some heartburn and we were not happy to see it go without being communicated
i think that the group field types are now in a stable place and we are going to immediately start taking breaking changes significantly more seriously
Roger that, thanks. I knew that y'all were going to move to true semantic versioning, and therefore didn't expect this breaking change, but it makes sense if this is the change that really sparked the need to do that.
Thanks for the explanation
Get help straight from the Payload team with an Enterprise License.