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
I'd normally expect mandatory fields to be mandatory on item/device instantiation
In [29]: classSubItem(HappiItem):
...: needed=EntryInfo('attr', optional=False, enforce=str)
...:
In [30]: subitem=SubItem()
<Someexceptionaboutmissingthe'needed'information>
Current Behavior
Currently "mandatory" (read optional=False) attributes/entries in a HappiItem are only enforced upon insertion through the CLI
I suppose this makes sense if the point of access is always the CLI, but if someone makes an entry interactively from Python (or is following the documentation's examples), this kwarg seems like a noop
Possible Solution
Be more consistent with complaining about missing, mandatory information?
Context
Briefly discussed during the 2022 Epics Codeathon, but put aside.
Your Environment
pcds-5.3.1
The text was updated successfully, but these errors were encountered:
Expected Behavior
I'd normally expect mandatory fields to be mandatory on item/device instantiation
Current Behavior
Currently "mandatory" (read
optional=False
) attributes/entries in aHappiItem
are only enforced upon insertion through the CLII suppose this makes sense if the point of access is always the CLI, but if someone makes an entry interactively from Python (or is following the documentation's examples), this kwarg seems like a noop
Possible Solution
Be more consistent with complaining about missing, mandatory information?
Context
Briefly discussed during the 2022 Epics Codeathon, but put aside.
Your Environment
pcds-5.3.1
The text was updated successfully, but these errors were encountered: