In the course of writing a user role condition plugin I stumbled upon the fact that in D8 users are STILL stdClass() objects. This is unacceptable from a purely cleanliness standpoint, but also no user contexts will validate for a stdClass() object when it's expecting a full user entity. TypedData won't validate for that either (which is actually the same problem) so we have to solve it.
I wanted to track these issues and try to scope them to some degree.
- This seems squarely D8 scope to me. We have a 3 k patch in another issue that should solve this.
- This seems mildly related, but I think the details of our changes in the above patch have impact here.
- Interesting topic suggesting we shouldn't have user 0 in the users table at all. I don't know if that's actually doable at this stage of development in D8 or if it should even be considered. The patch that belongs on the first issue in this list is actually posted here for the moment, and I'll be moving it shortly.
- The idea that perhaps there should be another API here: Users and Accounts. This seems squarely in D9 land at this point in development.
Please add more issues if you have them with a description of what they are. As we solve some of these perhaps other issues will become less critical or necessary.