Multiple guidelines about dscresources HOT 1 OPEN

Hi @iRon7
Thanks for the feedback, and we agree that the clarification is needed.

It's even more confusing because a lot of the guidelines and practices have been taken over by the DSC community and we'll be removing the DSC resource Style Guidelines you pointed to very soon, and link to the DSC Community one instead.

The reason for divergence between PowerShell and DSC is historic, and the main reason we keep some of those rules is that we have the PSSA rules to enforce some of them, and we want consistency across DSC resources rather than uncoordinated changes and discrepancies (most maintainers look after several resource modules).

Yes, we'd like to align with those Guidelines, but we want to have the tools to enforce them before we make the switch.

There's also more to it than it looks, we also want our tooling and documentation to support class based DSC resources before we can generalize its adoption.

By the way, we're always looking for contributors :)

from dscresources.