More opinions on mock organization #109
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@lathonez the reorg (#103) minimizes boilerplate, but please consider this alternative. For my app at least, putting all of the public methods for 30+ services in a single file is impracticable. When testing services consumed by multiple components, moving the mock out of the spec is DRYer. Ionic/platform mocks are still centrally in the
test/mocks.ts
but service mocks are in the same directory as the implementation.To make life easier I'm using barrels to provide encapsulation of services (definition) (import)
I think the same approach makes importing mocks easy as well