Skip to content
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

Support defaultEntityReference #122

Merged
merged 1 commit into from
Aug 29, 2024

Conversation

feltech
Copy link
Member

@feltech feltech commented Aug 27, 2024

Closes #53. Add support for the defaultEntityReference API method, which provides a way for hosts to get a "starting point" for further queries.

Add a new top-level dictionary to the JSON database defaultEntities, which has a mapping per access mode of trait set to entity reference.

If no matching trait set is found in the JSON database, then respond with kInvalidTraitSet. In real-world managers, an unrecognised trait set would probably elicit a response of None (for "no appropriate default"), rather than exception. But here we make a None response explicit by specifying null in the JSON database.

@feltech feltech self-assigned this Aug 27, 2024
@feltech feltech requested a review from a team as a code owner August 27, 2024 11:11
Copy link

@foundry-markf foundry-markf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly questions....

plugin/openassetio_manager_bal/bal.py Outdated Show resolved Hide resolved
schema.json Outdated Show resolved Hide resolved
tests/bal_business_logic_suite.py Show resolved Hide resolved
tests/bal_business_logic_suite.py Show resolved Hide resolved
Closes OpenAssetIO#53. Add support for the `defaultEntityReference` API method,
which provides a way for hosts to get a "starting point" for further
queries.

Add a new top-level dictionary to the JSON database `defaultEntities`,
which has a mapping per access mode of trait set to entity reference.

If no matching trait set is found in the JSON database, then respond
with `kInvalidTraitSet`. In real-world managers, an unrecognised trait
set would probably elicit a response of `None` (for "no appropriate
default"), rather than exception. But here we make a `None` response
explicit by specifying `null` in the JSON database.

Signed-off-by: David Feltell <[email protected]>
@feltech feltech force-pushed the work/53-defaultEntityReference branch from 4f54754 to 0b76500 Compare August 29, 2024 16:02
@feltech feltech merged commit 2f58d9b into OpenAssetIO:main Aug 29, 2024
12 checks passed
@feltech feltech deleted the work/53-defaultEntityReference branch August 29, 2024 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support defaultEntityReference
2 participants