Ignacio Hagopian

Currently, collections which have slice types in attributes can't be nil since operations will fail with`invalid schema`. We should fix this since in Go nil slices and empty slices are...

Mentioned by @sanderpick, to avoid DHT lookups.

Current txns are `Store`-wise, but the API has a model-working style, i.e. actions can be done only in a particular model. Change the API or add new API to have...

Currently there's a `JsonPatcher` implementation for creating events. Ultimately, using `rdoc` (or similar since since other languages requiriements are important) will be ideal.

See this package docs through `godocs` to improve package understandability/exporting/comments, etc

Think about some API to let clients catchup Thread log records starting from a particular height. This is important in users that can't skip records since the last _processed_ ones....

`badgerhold` (our base impl. of the query part of the eventstore) has a feature to build self-referencing queries. In our API that would mean something similar to: `.Find(.., Where('Name').Eq('Father.Name')`. Saying...

Sound reasonable to implement queries that can sort not only on one criteria: `.Sort('Field1', 'Field2', ...)`.

As mentioned by @carsonfarmer Consider it as a replacement for the currently underlying JSON schema and encoding. Notes: - pro: smaller encoded values - pro: faster validation of instance with...