Prove that discovery will spit back all resources of a handler, not just those registered
First stab: only return related resources. (not super pretty but not sure how to clean it up yet)
Still unsure how to make this better. At least tidy it.
That's the puppy
Added example to sample app
Can I see my operations if they use attributes over return types? No.
Prove attribute discovery does not work
Extend discovery heuristic to see if we really want to discover THIS type
Merge pull request #8 from antonjefcoate/duplicate_resources

Duplicate resources