Style Guide for classes #97

Activity

1. OCram85 commented on Nov 23, 2017

   

   OCram85

   on Nov 23, 2017

   More actions

   This post from @Xainey really helped me understanding classes and develop an own style.

   But I always struggle about things like this:

   • Is there a best case scenario when to define classes instead of creating PSCustomObjects and giving them a individual type name?
   • How complex should the class get? - How many different constructors do I need.
   • Should I use a class for combining different bbjects without any methods?

   So maybe it's worth thinking about a style guid for the syntax and a best practice for the usage itself?
2. vexx32 commented on Apr 20, 2018

   

   vexx32

   on Apr 20, 2018

   Contributor

   More actions

   I think the only time where I would consider it a mandatory requirement to have a class is for input validation where you need a specific type of object with a specific set of properties. I would also include a constructor that can take any PsCustomObject provided it has the right properties (and would otherwise throw an error), as well as one that simply takes all necessary properties as input.

   As for combining objects, I believe Join-Object is capable of this regardless. If you wanted this join to result in a different class, you could do the join in a constructor.