Error trying to delete an old components

[BR1G00]

If i delete a component from the config, but it is saved in the puck object, when i load the page where the component was, i can see "No configuration for [componentName]", but if i try to interact with it to delete it, the editor crash with this error.
I am on the last canary version "0.16.2-canary.525b506".

[the-code-raccoon]

Also ran into this issue too. At least to my knowledge there is no way for Puck to automatically deal with this case. Instead I wrote a function that checks over all components in the raw puck data before rendering it or opening it in the editor

const filterUnknownComponents = (puckData) => {
  const config = getPuckConfig()

  return {
    ...puckData,
    content: puckData.content.filter((item) => config.components[item.type]),
  }
}

[chrisvxd]

Thanks @BR1G00, I also encountered this one. Marked as a bug and ready.

[chrisvxd]

@BR1G00 think this might actually be fixed in canary via #665. Could you confirm?

[mkilpatrick]

Can confirm this fixes it.

[BR1G00]

#665

@chrisvxd Before that commit I couldn't even see "No configuration for [componentName]", after that I can see the component, but when I click on it it crashes with the attached error

[chrisvxd]

Apologies, your issue description mentions that canary. Will keep this open.

[chrisvxd]

@BR1G00 this should be out in latest v0.16.2 canary as soon as deployed