Construct Component With Pre-Created Entity

[dOrgJelli]

This will make sure ComponentLists that render Components do not double query a single entity.

[dOrgJelli]

So after thinking about this a bit more, I think it makes the most sense to update to Client 2.0, and then tackle this. This is because, in Client 2.0, each class has a coreState property which stores the data of the entity. This data is the result of the query we're trying to make sure we don't double execute.

The logic (post client 2.0 upgrade) for ensuring we don't double query when using ComponentLists is this:

1. For example, given the component list <DAOs>
2. Within ComponentList query DAO.search(...) (like we already do)
3. When we iterate through the resulting DAO[] collection and render the <DAO> component, we pass in the prop _entity, which will be a DAO item from the DAO[] collection.
4. Within Component, when the prop _entity is provided, we don't need to create an entity and instead we just use the entity given. This will hopefully make sure a double query is not made, because Component will use the entity.fetchState() function which will return coreState if it exists.

In order to verify this doesn't double query for a single entity state, we should setup an automated test. How exactly this test will work I'm still not sure. Should we check to make sure Entity instances are the same? Should we measure the number of queries? Should we reach into the Entity[] collection's data and set a know "good" value that we later check for when we get Entity.Data to make sure our set value doesn't get overwritten by the query?