Jon Freer
Jon Freer
Hey there 👋🏼 ! Choosing to file a bug report, as it's unclear whether this project considers incorrect / misleading documentation as a bug. As currently written, the YAML ->...
**Description** Takes on #24! **Rationale** This feature unlocks the ability to prevent loading the same object (entity) from the applications data store. At the same call sites as `#Register`, consumers...
**Description** Another well known design pattern presented by Martin Fowler is known as the [Identity Map](https://www.martinfowler.com/eaaCatalog/identityMap.html). Although very straightforward, this pattern can be incredibly powerful, as it reduce unnecessary round...
**Description** Removes the code responsible for supporting V1 / V2 of the package. **Rationale** With the introduction of V4, these versions are now in unsupported territory. These versions did not...
After investigating the latest documentation for `zap`, there is a [constructor](https://godoc.org/go.uber.org/zap#NewStdLog) that wraps a `zap.Logger` with `log.Logger`. Since `log.Logger` is a part of the standard library, it would be best...
**Description** By nature, the sequence that occurs in order to successfully save or rollback is well suited for being managed by a `stack` data structure. In general, construction of the...
**Description** Introduces support for consumers of `work` to provide their own cache clients in the event they wish not to use the default in-memory caching. For example, users may provide...
**Description** Clear and concise description of the changes. Make sure to include any open issues that these changes aim to resolve. **Rationale** Rationale of why consumers need this feature or...
## BACKGROUND As brought up in #57, the project lost steam just prior to releasing V4. this version bring along a lot of benefit to usability and feature sets. ##...