You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why
Right now the COSMOS API is too intertwined within HMI. So that if the API breaks or evolves, we have to update multiple parts.
i.e. #200, the CosmosSearchObjectsInterface and CosmosArtifactInterface are consumed similarly, but they are entirely different types; which creates unnecessary tests to handle both of them.
How
Create a Class wrapper (or another mean) to consume COSMOS API.
Why
Right now the COSMOS API is too intertwined within HMI. So that if the API breaks or evolves, we have to update multiple parts.
i.e. #200, the
CosmosSearchObjectsInterface
andCosmosArtifactInterface
are consumed similarly, but they are entirely different types; which creates unnecessary tests to handle both of them.How
Create a Class wrapper (or another mean) to consume COSMOS API.
Source
Integration with COSMOS and xDD — ASKE, Uncharted Google Docs
The text was updated successfully, but these errors were encountered: