-
Notifications
You must be signed in to change notification settings - Fork 284
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
Specific unit testing of Cube.coord_dims
#4552
Comments
The way this currently works, we do have tests for the
These are all, actually, basically the same thing, but it is implemented like this because Cube doesn't provide a method to access an arbitrary 'dimensional cube component', equivalent to a _DimensionalMetadata.
I guess the Cube API is done this way, just to make the public Cube API methods explicit, and not too abstract. |
Although the unstructured support has now added Connectivity as a subclass of _DimensionalMetadata, and that does not relate to cube dimensions in the same way -- and so, interestingly, its |
This, you may recall, is why @bjlittle has recently mentioned restructuring the inheritance model for |
In order to maintain a backlog of relevant issues, we automatically label them as stale after 500 days of inactivity. If this issue is still important to you, then please comment on this issue and the stale label will be removed. Otherwise this issue will be automatically closed in 28 days time. |
This stale issue has been automatically closed due to a lack of community activity. If you still care about this issue, then please either:
|
📰 Custom Issue
Currently there isn't specific unit testing of
Cube.coord_dims
. I'd like to see this change.Suggested coverage:
The text was updated successfully, but these errors were encountered: