-
Notifications
You must be signed in to change notification settings - Fork 28
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
[C++] resolve
method host conveniences
#849
Labels
Comments
feltech
added a commit
to feltech/OpenAssetIO
that referenced
this issue
Mar 24, 2023
Part of OpenAssetIO#849. In preparation for assigning `BatchElementError` objects to each other (e.g. setting in a container), we must ensure its members are not `const`. Signed-off-by: David Feltell <david.feltell@foundry.com>
feltech
added a commit
to feltech/OpenAssetIO
that referenced
this issue
Mar 28, 2023
Closes OpenAssetIO#849. Previously, the only interface to `resolve` assumed a batch of entity references with success/error callbacks executed for each element. This is somewhat clunky when only resolving a single reference in particular, and requires significant boilerplate. So add convenience overloads that present the API in a friendlier and more versatile manner. As resolve conveniences in C++ and Python are going to be somewhat distinct, add C++ tests to verify behaviour of `variant` and exception error modes. Signed-off-by: David Feltell <david.feltell@foundry.com>
elliotcmorris
pushed a commit
to feltech/OpenAssetIO
that referenced
this issue
Mar 30, 2023
Part of OpenAssetIO#849. In preparation for assigning `BatchElementError` objects to each other (e.g. setting in a container), we must ensure its members are not `const`. Signed-off-by: David Feltell <david.feltell@foundry.com>
elliotcmorris
pushed a commit
to feltech/OpenAssetIO
that referenced
this issue
Mar 30, 2023
Closes OpenAssetIO#849. Previously, the only interface to `resolve` assumed a batch of entity references with success/error callbacks executed for each element. This is somewhat clunky when only resolving a single reference in particular, and requires significant boilerplate. So add convenience overloads that present the API in a friendlier and more versatile manner. As resolve conveniences in C++ and Python are going to be somewhat distinct, add C++ tests to verify behaviour of `variant` and exception error modes. Signed-off-by: David Feltell <david.feltell@foundry.com>
2 tasks
elliotcmorris
pushed a commit
to feltech/OpenAssetIO
that referenced
this issue
Mar 31, 2023
Part of OpenAssetIO#849. In preparation for assigning `BatchElementError` objects to each other (e.g. setting in a container), we must ensure its members are not `const`. Signed-off-by: David Feltell <david.feltell@foundry.com>
elliotcmorris
pushed a commit
to feltech/OpenAssetIO
that referenced
this issue
Mar 31, 2023
Closes OpenAssetIO#849. Previously, the only interface to `resolve` assumed a batch of entity references with success/error callbacks executed for each element. This is somewhat clunky when only resolving a single reference in particular, and requires significant boilerplate. So add convenience overloads that present the API in a friendlier and more versatile manner. As resolve conveniences in C++ and Python are going to be somewhat distinct, add C++ tests to verify behaviour of `variant` and exception error modes. Signed-off-by: David Feltell <david.feltell@foundry.com>
elliotcmorris
pushed a commit
to feltech/OpenAssetIO
that referenced
this issue
Apr 3, 2023
Part of OpenAssetIO#849. In preparation for assigning `BatchElementError` objects to each other (e.g. setting in a container), we must ensure its members are not `const`. Signed-off-by: David Feltell <david.feltell@foundry.com>
elliotcmorris
pushed a commit
to feltech/OpenAssetIO
that referenced
this issue
Apr 3, 2023
Closes OpenAssetIO#849. Previously, the only interface to `resolve` assumed a batch of entity references with success/error callbacks executed for each element. This is somewhat clunky when only resolving a single reference in particular, and requires significant boilerplate. So add convenience overloads that present the API in a friendlier and more versatile manner. As resolve conveniences in C++ and Python are going to be somewhat distinct, add C++ tests to verify behaviour of `variant` and exception error modes. Signed-off-by: David Feltell <david.feltell@foundry.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implement host conveniences for
Resolve
for the C++ api.Resolve exists already in the C++ api, so does not need porting or deep redesign.
Refer to #848 for criteria.
ACs
Return
policyThe text was updated successfully, but these errors were encountered: