-
## Background
The Entity API was built out of the necessity for decoupling the hooks API. One thing that has been needed as a part of that API is the ability to restrict the display of points logs ba…
-
> _Original title: Conditions and Entity Arrays_
## Background
### API
During the work on the post terms Condition, the Entity API was born (originally christened the Args API). One part of it was th…
-
From https://github.com/WordPoints/hooks-api/issues/59#issuecomment-167158832:
> The only thing we need to consider is events with multiple args. Since there really is no concept of "main arg" in the…
-
## Background
In the process of building this I've introduced the WordPoints App class, which is basically just a collection of object registries and sub Apps.
There is a main App that acts as the h…
-
The periods extension was built without any specific provision for multisite and network periods. Because of this, it currently isn't multisite compatible. The intention of this ticket is to explore h…
-
While working on #42, I've discovered that the post publish hook does not fire for attachments. This affects the old post publish points hook as well. So apparently it has never worked.
The reason fo…
-
## Origin
The Entity portion of the Hooks API started out being called the "Args API". The name was derived from the fact that the values for the Entities come from the arguments that an action was c…
-
An addition to the entity API which disclosed how entities were stored is something that we have been contemplating since early on. It was a necessary dependency of the entity query API (#1). However,…
-
-
The reaction class currently includes `create()` and `delete()` methods. In this issue I'd like to explore the possibility that we should remove them.
The biggest problem is with the `create()` metho…