Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove mocks from all client services #2372

Closed
brandonforster opened this issue Feb 13, 2020 · 0 comments
Closed

Remove mocks from all client services #2372

brandonforster opened this issue Feb 13, 2020 · 0 comments
Labels
1-low priority denoting isolated changes enhancement New feature or request help wanted Extra attention is needed unscoped Issues that are currently out of scope for all releases.

Comments

@brandonforster
Copy link
Contributor

🚀 Feature Request

Description

Currently, EdgeX contains at least one mock for a service defined in go-mod-core-contracts. A PR was started in that repo to update it (edgexfoundry/go-mod-core-contracts#215) before deciding that it actually made more sense here (see #2370 for context.)

This is a better bad solution. The best solution would be to remove mocks entirely. This issue attempts to capture that work.
@brandonforster brandonforster added enhancement New feature or request unscoped Issues that are currently out of scope for all releases. labels Feb 13, 2020
@michaelestrin michaelestrin added help wanted Extra attention is needed 2-medium priority denoting issues with cross-cutting project impact 1-low priority denoting isolated changes and removed 2-medium priority denoting issues with cross-cutting project impact labels Feb 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1-low priority denoting isolated changes enhancement New feature or request help wanted Extra attention is needed unscoped Issues that are currently out of scope for all releases.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@michaelestrin @brandonforster @JamesKButcher