Add name argument to add_component

bringing up this thread again - clarification on the clarification…

Is it the recommended approach because name_conflicts or another reason…

I see the tag component as super useful and a convenient place for certain things.
Especially for components that are not a Form which is when I tend to use it most…

But for a Form I don’t typically use it because it rarely seems pythonic to me.
(apart from when it does :thinking: )
I think your initial post @bridget, to me, seems the preferred way to do something like that…

in this post from a few years ago @ian mentions the phasing out of directly adding attributes to components. Also linked above
But like @stefano.menci mentions its also used for most tutorials and in most situations seems like the best approach…

"Safe" names for developer-defined object members - #2

Is there a distinction here between components that may have something like this phased out…
Surely the Form will never have this phased out since it’s a python class with a __dict__