Cmdlets for List Rules and Quick Steps - what would be sufficient for a v1 first set of cmdlets?

[iainwyatt]

I wanted to automate the creation of quick steps on a library in a project but found they're not covered yet :) They are in the same API as rules. A start was made on a feature request but it seemed to get confused with alerts - #5039 . I found the code in #5123 and have started a fork with a copy of the code at that point to have a look at it.

The basic code to get rules may be straight forward but I feel like the cmdlets to set Rules or Quicksteps is going to need some robust logic to ensure they are set properly. I've had a look at the code and got some enums in place (found in js on the page) and updated some properties so functionally I can build and run the code. :) So far I can return some rules :)

Do we have a community view about how robust the cmdlets should be? Could they be open so that a user can set the logic string themselves in raw form and not thus worry about constructing it for them as a first pass of the cmdlets to get something functional with care and caution available?

Thanks.