'noop' component in the model which prevents saving

I saw this today too, but chalked it up to me removing, adding, and refactoring props and slots on the fly without any regard for B/C.

For the most part XB seemed to be pretty forgiving, but I did run into this a couple times.

Without steps to reproduce this is a tricky one to address. There are a few instances of 'noop' in the XB FE codebase. At a guess I would suggest something like the props of an instance of a component on the page are being changed but the component is unknown. (unknown because the list of components was not loaded yet/failed to load or the component has been deleted since it was added?).

However in response to:

Should the frontend remove components from model that are not in the layout so that content can be saved?

I think that the error handling/robustness should be on the server side, not the client. Kinda following the idea of 📌 Improve server-side error handling Active .

I've not seen this in months at this point so I think it would be fine to close this as outdated. We probably need a follow-up to handle this more generically in the backend still.