Andrew Hodgkinson
Andrew Hodgkinson
When Hoodoo is receiving a request into a known set of interface declarations, then if using a test session, only the interfaces' declared resources and supported actions of those resources...
Formalise a simpler way for service authors to create Mock Resources for testing calling remote resources. See the Testing Guide for the current approach. The correct for this might be...
PR https://github.com/LoyaltyNZ/hoodoo/pull/229 introduces a test dependency on WebMock for expediency, but only uses it for this one test alone. It's a heavy dependency to pull in for that one use...
https://github.com/LoyaltyNZ/hoodoo/pull/223 introduces `acquire_in`, which adds errors to the given `context` automatically. This arises from the addition of `generic.contemporary_exists`, which would cause quite high and error-prone service implementation complexity if no...
Hoodoo doesn't yet offer any support at all for "_embed"/"_reference" implementations. For services wishing to enforce permissions, inter-resource call permissions augmentation makes life difficult - a "several hops downstream" resource...
DSL for `embeds` - make it accept a Hash where a better structure is provided, e.g. with :comment for docs? [Andrew Hodgkinson]
Perhaps e.g. go with `return ...` and the returned item is either auto-rendered, or is the rendering of the resource, but either way no explicit `context.response.set_resource`. It's implicitly singular for...
As title. When working on a hotfix for v2 I tried upgrading the Rack patch to a Hoodoo class instance monkey so that the aliases for the original Rack `start`...
Hoodoo understands "expected duplications" via `X-Deja-Vu: yes` in a request (or `endpoint.deja_vu = true` if using `Hoodoo::Client`) but only signals that a duplicate violation exception was returned by the database...
In `Hoodoo::Services::Response`: * https://github.com/LoyaltyNZ/hoodoo/blob/master/lib/hoodoo/services/services/response.rb ...there was originally just a `#body` accessor used to set response data, but this was later improved with some higher-level names of `#set_resource` and `#set_resources`. These...