Deprecate parts of Container.retrieve
- Current behavior is not documented
- When an entity with the same name but another role exists, an error occurs
- unclear what errors are covered by
raise_exception_on_error, mismatch of role is not - Entities are also retrieved based on their path, which is not documented.
- Behavior when names are not unique is unclear (Is the current entity update? 1 local, 2 remote -> 3 entities returned?)
Intended behavior: For each entity in the container, replace it with the remote version if possible:
- if the entity has an ID, get that entity
- if the entity has a name, try to get the entity via name
DoD:
- deprecate query keyword of Container.retrieve
- deprecate raise_exception_on_error
- deprecate unique = False
- update docstring
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
No child items are currently assigned. Use child items to break down this issue into smaller parts.
