-
Publish artifacts as release assets when we do a release.
### Why
We want to use these for pinning, in order to enable multi-platform workflows. See https://github.com/OpenAssetIO/OpenAssetIO/issues/…
-
## What
As a developer working with OpenAssetIO I need a sample implementation(s) of the `ManagerInterface` that can be used via the `PluginSystemManagerFactory`. They need to demonstrate canonical…
-
# What
Improve tests of header location and compilation to catch implicit dependencies between them
# Why
Simply having a long list of `#include`s risks earlier headers inadvertently providi…
-
## What
Following on from https://github.com/OpenAssetIO/OpenAssetIO-TraitGen/pull/12#discussion_r1133597508. Pin versions of linters used in CI checks. Document a process for regularly updating li…
-
https://github.com/TheFoundryVisionmongers/OpenAssetIO/pull/353#discussion_r859535937
-
## What
This was noticed in the usdResolver, but I think it's an OpenAssetIO problem so logging here.
We have code in the usd resolver tests that triggers a python exception, and attempts to verify …
-
## ACs
- The template illustrates a b1 compatible plugin.
- Support old `TraitsData` import for compatibility with docs
- Tests run against versions either side of `TratsData` deprecation
-
## What
The current situation with our python deps is tying us in knots:
- MediaCreation lists `openassetio` as a dependency, this means that anything that uses MC then forces an install of `openass…
-
Currently pinned to `alpha.10` untill TraitGen without `TraitBase` is released.
-
Following on from #47, and based on our eventual Python 2 vs. 3 vs. C++ design decisions, we should add a section to the documentation detailing how string encoding is handled in OAIO.