Skip to content

All IOpProcessors should accept every level of service layer interface #383

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jaredcnance opened this issue Aug 24, 2018 · 1 comment
Closed
Milestone

Comments

@jaredcnance
Copy link
Contributor

Description

public GetOpProcessor(
IGetAllService<T, TId> getAll,
IGetByIdService<T, TId> getById,
IGetRelationshipService<T, TId> getRelationship,
IJsonApiDeSerializer deSerializer,
IDocumentBuilder documentBuilder,
IContextGraph contextGraph,
IJsonApiContext jsonApiContext)

All IOpProcessors should provide a constructor overload that accepts IResourceService and IResourceCmdService or IResourceQueryService

@jaredcnance
Copy link
Contributor Author

Closing in favor of #394 and #384

If we register all forms automatically, there should be no need for these overloads...

@jaredcnance jaredcnance removed bug operations json:api v1.1 operations labels Sep 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

1 participant