Add a 'disabled' section to config changes page when removing config

For me, this issue might be wontfix, and we should instead focus on how to actually communicate to users what config is being updated or deleted

@xjm oh, really? Thank you, but no, we shouldn't!

I lost recently a day of local work while just tried to use views_natural_sort module in my views.
The same as here https://www.drupal.org/project/better_exposed_filters/issues/2992372#com... 🐛 When module uninstall, view is deleted Active
And don't say me that I should backup such things!

I'm sorry but I feel myself very upset.
I wish nobody never get into this situation.

Why not just introduce "trash bin" concept without restoring, just to store any config deletions! Let's say "config_deleted" or "config_r__0ab2f8e96b" and so on?

If you're not going to fix this.. at least put in a graphic of a thug with a crowbar breaking a computer or something severe. First timers are almost 100% not likely to get the extent that they will lose their views. In my case, I lost the built in Content view that lets me search content from the back-end administration page. Luckily my test site hasn't been changed yet, and still has the view. I'm not exactly sure how easy it will be for me to eyeball-copy/create it from two browser windows. Is there a better way to extract/import views? If the infrastructure doesn't play well with disabling views.. can you make it easy to export a view to json and import a view from json? Perhaps export all deleted views to a .json file for backup?

I just came across this as a very recent user to D9/10. I deleted a field from a Content Type and it broke the Views that were using it. Very annoying to say the last, but more importantly it's a recipe for disaster. I also found I cannot simply edit the broken View and remove the same field from it to fix it quickly. The old fields are not visible on the View edit page any more!

The View was disabled which was helpful to understand what had happened, but can you not configure it such that a reference to the broken field is still visible allowing easy removable from the Views edit page?

I feel with the last three commenters, which confirms my thinking -- giving only an easily missed warning for the deletion of a View, instead of a hard blocker á la when uninstalling Forum module, is a recipe for disaster, and I just posted this in 🐛 View deleted without notice on deletion of content type Needs work :

Whenever a new Drupal user encounters a silently deleted View, after spending many hours, or maybe even days painstakingly building it, it's a disaster. The majority of these new users probably don't use version control, and commit every so often, so the hard work is basically lost for good. Even if they did, restoring it could be difficult. I wouldn't be surprised if some new users get so fed up with Drupal, that they leave it behind, or at least are left with a bitter taste in their mouth.

Also, saw this in 🐛 When deleting a content type field, users do not realize the related View also is deleted Fixed :