Closed ghost closed 8 years ago
I guess there really isn't a good use case for this. Closing.
I think of events going into the EventServer as always a tuple (user-id, event-name, item-id) where the item type is inferred by the event-name. This is the most minimal way to represent these.
This makes the targetEntityType superfluous, and therefore ignored. It is only used because it is needed by the framework, not because it holds any meaning so I agree, no real need.
Rather than defaulting to
user
anditem
in code, I've moved theentityType
andtargetEntityType
configurations to the engine's JSON file and provided parameter defaults. I've also cleaned up the README's spacing and fixed two minor esClient issues (an unneeded import and using"items"
instead of theindexType
param).