[meta] Drupal 8 Entity API improvements

Looks superb. Tagging DX and D8MI.

Updated issue summary.

Also tagging cmi. Looks great.

Another thing we will want to look at is how we're going to introduce UUIDs into entities. I will probably make a new issue for that as well. I think it makes sense for this to happen after all the entities are converted maybe?

From #1184944-151: Make entities classed objects, introduce CRUD support:

While we're waiting ;) it'd be great to open the follow-up issues for this and document them in the issue summary, I can think of the following but might have missed some too:

- converting all the different core entities apart from Comment.
- adding revision support to the base controller (which will need co-ordination with #1082292: Clean up/refactor revisions)

I don't see revision support explicitly listed above. I'm assuming it would be an additional item in step 1, before we start on the other entities?

Implement full revision support in the database storage controller

You're right, though, we need that to convert nodes.

when re-factoring revisions take a look at #218755: Support revisions in different states
It's not much different from #1082292: Clean up/refactor revisions

(xjm) Added @todos from #1184944 and added header tags.

Alright, I moved the note about revision support up to Step 1.

Cross-referencing:

• #430886: Make all blocks fieldable entities

I'd love to see those follow-up issues classified as major "feature requests" rather than tasks. It's not really very equitable to the rest of the team for a single initiative to block progress on all other initiatives by pushing us up over thresholds by splitting up the work into sub-issues.

Totally cool with this issue remaining a major task, though.

Ah, yes, +1 for switching them to feature requests. They are kind of bullying major tasks at the moment. :) I've switched them to feature requests for now, unless someone disagrees?

I'm fine with downgrading the individual issues from major task, but think we should open a single critical issue (not this one which is about further API additions/changes) to track them.

Converting existing entities to the new API is essential to uncover issues with what we just committed (as we found out at length with field API), and needs to happen earlier rather than later in the cycle (and it's critical to update all core entities before we get to release, so critical feels about right for that).

Well, if we want to make real use of the OO API (introducing language consistently as well as adding UUID support), we should do the conversion sooner than later. So I hope it is not just done later up to the release :) Or if the OO conversion is to be delayed, we should add UUID and language with the old methods and the conversion will be just more work that way. Not sure its better in that direction.

Yeah I couldn't agree more, opened #1368394: Convert all core entities to classed objects.

I added #1374030: Remove entity_extract_ids() now that we have proper classed entity objects to the todo list

Added issue

Added #1374116: Move bundle CRUD API out of Field API

Added http://drupal.org/node/1374116

It would be very nice if we could actually keep entity_label() around. It works very well as a title callback for menu router items.

Actually, I would like to keep entity_uri as well for similar reasons.

added 1391694

I've added #1346204: [META] Drupal 8 Entity API improvements to the summary.

That's recursive ;) Not that I can talk, I've marked dozens of issues duplicate of themselves...

Move to new D8MI-meta tag.

Tagging.

Updated issue summary.

Couple followups from the user conversion:
#1537434: Add type-hinting to user entities
#1537442: Rename $user->access and $user->login

Edit: I didn't know where to put these on the roadmap in the summary. :)

Do we have to make an issue to convert

"field_test_create_stub_entity"

At the moment it returns a stdObject but this is incorrect. It should return a proper entity.
That also blocks some followups like remove entity_label().

Problem: it sometimes adds a version ID which is only possible for nodes.

First stab to the Entity form system in #1499596: Introduce a basic entity form controller. Early reviews welcome :)

Updated issue summary.

Opened #1615236: Merge entity controller interfaces, document and add default entity class definition and added it to step #2.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Added the first issue on the entiy form system.

Updated issue summary.

Updated issue summary.

referenced the entity_uri issue

typo

We achieved almost everything of this, yay! Now we need to complete it, there's a new meta for this, see you over in #2095603: [meta] Complete Entity Field API.