-
Couldn't load subscription status.
- Fork 6
feat: Add option to connect as mock devices #1245
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1245 +/- ##
==========================================
+ Coverage 94.67% 94.75% +0.07%
==========================================
Files 41 41
Lines 2611 2612 +1
==========================================
+ Hits 2472 2475 +3
+ Misses 139 137 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Do you have a use case that requires this? To my mind this should be tracked in the dodal module, as the device_factory allows setting whether to connect sim or not, rather than having multiple potentially overlapping places to define this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's currently no way (that I'm aware of?) of marking all device factories as mocks in one change so I can see the motivation for being able to mock an entire beamline in one flag.
This is all about to change though if the device manager change works out so it might be easier to change there? Other than the weirdness it introduces around having mock plans, I'm not against the idea of it being here as well though.
| "kind": "planFunctions", | ||
| "module": "dodal.plans" | ||
| "module": "dodal.plans", | ||
| "mock": false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having a mock field on a plan module is odd. Can we split the Source type into a union where each sub type only has relevant fields?
No description provided.