Skip to content

methods with v1/2 restrictions should check version and give informative errors #216

Description

@tmchartrand

@dbirman just clarified for me that some of the QC metadata helper methods only work for v1 metadata. This is currently only enforced very loosely by restricting the dependency version in the "helpers" dependency group.

However, the helpers methods are still available even without this group installed, and the same endpoint can be reached via MetadataDbClient directly in addition to the helpers methods - this code needs to explicitly check the client version before making such a request, and raise an informative "not supported" error.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions