Unincluding a space doesn't highlight spaces cascade

[colmjude]

When a user unincludes a space, lets call it space X, the UI used to inform the user about the other spaces that the had been included when X was first included. I.e. all the spaces X includes.

This allowed the user to be able to make an informed decision about which spaces to keep or which still needed to be removed. This no longer exists and causes confusion for users.

[cdent]

If I recall correctly the old code used to retrieve the recipe of the unincluded space and parse it for bag names that look like space names (those that match /(.*)_public$/) and use $1 to flag the remaining spaces. So that would mean:

• GET /recipes/<included space>_public as JSON
• parse the recipe list
• add some kind of class to elements in the includes list

[pads]

What about the following: Any new tiddlers an included space brings in are tagged with a keyword such as imported_from_spacename. You could then easily see what was left behind to spring clean either by hand or by program.