-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Docs] Add Jupyter Notebook illustrating entityTraits #69
Conversation
7d906b2
to
9f1619e
Compare
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.
Fantastic doc 👍 great way to flesh out and stabilize the design before implementation. A few random comments fwiw.
Btw - a nice thing here is by the time the work is done and this is passing we should have some usefull specifcations from #22 |
37246ed
to
9a9acd0
Compare
Discovered whilst updating OpenAssetIO/OpenAssetIO-MediaCreation#69 after OpenAssetIO/OpenAssetIO#1217. The API docs for `resolve` say > Only traits that are applicable to each entity, and for which the manager has data, will be imbued in the result. However, if an entity in the JSON library has a trait as part of its trait set, but that trait has no properties (either because that trait has no associated properties, or because it's not set in the JSON), then it was imbued in the `TraitsData` regardless. Signed-off-by: David Feltell <david.feltell@foundry.com>
f67eac0
to
cf630c3
Compare
Update on this rather long-running notebook(s). It's updated to use the changes in OpenAssetIO/OpenAssetIO-Manager-BAL#90 and is working nicely. CI still targets PyPI releases for dependencies however, so either we need to retarget it, or wait til the next release, before this PR can be merged. |
6df8e78
to
e94f7c9
Compare
e94f7c9
to
66703d4
Compare
66703d4
to
5788493
Compare
5788493
to
7422704
Compare
Part of OpenAssetIO/OpenAssetIO#31. This notebook was originally used to sketch out the design of the `entityTraits` API method, elicit discussion, and come to a shared understanding of the feature as a team. Being an executable document, the notebook now functions as tested documentation and an e2e test suite for the feature, utilising the OpenAssetIO ecosystem beyond the core `entityTraits` API method (i.e. convenience signatures, BAL, `managementPolicy`). Signed-off-by: David Feltell <david.feltell@foundry.com>
Part of OpenAssetIO/OpenAssetIO#31. This notebook came as an appendix to illustrating usage of `entityTraits` in the original design notebook for that API method (see previous commit). However, during review it became apparent that a generic resolve and republish workflow is a distinct use-case, and not specific to `entityTraits`. So it was moved to its own notebook. Signed-off-by: David Feltell <david.feltell@foundry.com>
7422704
to
0530d4b
Compare
Add a notebook illustrating the usage of
entityTraits
, as specified in OpenAssetIO/OpenAssetIO#31.Add another notebook illustrating advanced usage of
entityTraits
in a generic resolve-and-republish workflow.The idea in the first instance is to provoke discussion and provide a reference as the feature is further refined.
An ideal outcome is that this document continues to be iterated as the feature(s) is developed, incorporating changes in design as well as new corner cases that need defining.
Eventually this should lead to an executable specification of the feature, which also serves as example documentation.
Dependencies
The notebook has dependencies on work in other repos, in particular
Manager.entityTraits
method OpenAssetIO#31kManagerDriven
andkRequired
toPolicyAccess
OpenAssetIO#1209entityTraits
OpenAssetIO#1217entityTraits
OpenAssetIO-Manager-BAL#89