You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To avoid making circular imports it would be good to make some rules and add a linter as per DiamondLightSource/mx-bluesky#568 but with the config in a TOML file.
The rules:
epics depends only on core
tango depends only on core
sim depends only on core
fastcs depends only on core, epics, tango
plan_stubs can depend on anything
Acceptance Criteria
Anything that breaks the above rules errors pre-commit
The text was updated successfully, but these errors were encountered:
should plan_stubs be generic though? separate tango and epics plan stubs?
Hmm, interesting point, in fastcs we do try/catch imports of epics and tango, and epics works even without the relevant transport, but tango doesn't. This will work at the moment but we might find this breaks in the future.
To avoid making circular imports it would be good to make some rules and add a linter as per DiamondLightSource/mx-bluesky#568 but with the config in a TOML file.
The rules:
Acceptance Criteria
The text was updated successfully, but these errors were encountered: