Make Policy
and Template
APIs consistent wrt annotations
#1116
Labels
feature-request
This issue requets a substantial new feature
Category
User level API features/changes
Describe the feature you'd like to request
As noted in this TODO in the code
PolicySet
has two methodsannotation()
andtemplate_annotation()
which are very similar except that one expects a policy ID and one expects a template ID. However, the former returnsOption<&str>
and the latter returnsOption<String>
. We should make this consistent; I thinkOption<&str>
is better.Describe alternatives you've considered
We could converge on
Option<String>
instead.Additional context
No response
Is this something that you'd be interested in working on?
The text was updated successfully, but these errors were encountered: