Group Field Breaking Type Changes not Called Out

default discord avatar
7 months ago

@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:

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?

  • discord user avatar
    Payload Team
    7 months ago

    Hey @TheDunco - yes, this change in specific is what led us to want to embrace


    semantic versioning

    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

  • default discord avatar
    7 months ago

    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

Open the post
Continue the discussion in Discord
Like what we're doing?
Star us on GitHub!


Connect with the Payload Community on Discord



Can't find what you're looking for?

Get help straight from the Payload team with an Enterprise License.