Would you ever use multiple Custom Features per command

[mcd8604]

I was pondering if I would ever need to create more than one Custom Feature for a Command. I can't think of any use cases for this and am wondering if anyone else can come up with one. The reason I am asking is because I am creating a wrapper class which will encapsulate the create/edit CommandDefinitions and a single CustomFeatureDefinition. I am just not sure if I should add support for multiple Custom Features now or later when the situation arises.

[florian.pommereningDGUYA]

I also starting building a wrapper for this. If you want to compare the approach, my code is here: https://github.com/FlorianPommerening/FingerJoints/blob/experimental-custom-feature/commands.py

It might be a bit out of date if the API changed after I last looked at this.

I also chose to stick with a single custom feature but I can imagine a case where you'd want more: if the command batch-creates multiple things that you later want to edit independently. For example the add-in I linked creates a finger joint between two parts. One possible extension would be to give it a bunch of parts and let it create joints between all of them. But then  maybe you later want to make changes to the settings of an individual joint. I don't think this is critical, though. It would be just as useful or maybe even better to make changes to all created joints at once.