Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Thoughts on traits selection in ValidateSetPropertiesByPath() and SetPropertiesByPath() #14

Open
Pete-Cordell opened this issue Jul 5, 2024 · 0 comments
Open

Thoughts on traits selection in ValidateSetPropertiesByPath() and SetPropertiesByPath() #14

Pete-Cordell opened this issue Jul 5, 2024 · 0 comments
Labels
enhancement New feature or request triage Apply to all new issues

Comments

@Pete-Cordell
Copy link

Pete-Cordell commented Jul 5, 2024 •
edited
Loading

I suggest renaming includedPropertyTraits to propertyTraitsFilter and make it nullable (i.e. sequence<NcPropertyTrait>? propertyTraitsFilter).

Then describing propertyTraitsFilter as:

propertyTraitsFilter - If non-null, specifies that only role paths with the traits specified by this property are to be validated / restored. If the parameter is null, the operation should proceed as if this property was set to "General", "Structural", "InstanceSpecific", and "DeviceGenerated" thus invoking a full restore.
@Pete-Cordell Pete-Cordell added the enhancement New feature or request label Jul 5, 2024
@github-actions github-actions bot added the triage Apply to all new issues label Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request triage Apply to all new issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Pete-Cordell