You should not worry about it.  Those are deployment instructions, they are not a setting that is connected to how you actually deploy it.  And we did recently change it to show async by default (we are encouraging people to make that move), but it's still just instructions.You have Target on your C...

It is still on the roadmap yes.  We've shuffled some of the priorities, so it will come later than originally planned, but it will come.

Your suggested alternative is a good idea.  It was discussed as part of the original development scope, but it's just a lot more work and we wanted to make delete available as quickly as possible (since so many people were asking for it).  We may eventually do this as an enhancement to delete.

Sorry for the confusion, I'll try to explain a bit about how the system works.Every resource (data element, rule component, etc) has an identifier for it's parent, meaning, it knows which Extension provided it.  The extension providing the resource (in this case the Core Extension) is identified by ...

When you uninstall an extension and reinstall, the new installation gets a new ID and is considered a new extension.  So the data elements, etc not displaying is expected because this extension is a new one.So yes, you shouldn't uninstall an extension unless you plan on getting rid of the extension ...

For now, disabling is the best you can do.  We expect the Delete functionality to be available in the next 2-3 weeks.

Yes, it's being worked on now.  Will be released in January.  In the meantime, the best you can do is disable them.  Once disabled, you can filter the list views to now show you disabled things.  The filter will persist for your user session.

It does now, although they are separate data element types after you select the Core Extension.

Here now: Launch Object Reference

I just saw a demo of a Page Info data element type (provided from the core extension) to give you these options.  Will release in Q1 sometime.