Make App's `showView()` more consistent when working with new vs. existing views. about yui3 HOT 5 OPEN

I vote for option 4. update adds unnecessary magic.

from yui3.

While removing functionality that people might be using could cause some headaches for some I agree with @rgrove

from yui3.

@hatched If I go with option 4 I would first deprecate the feature, log a warn if it is used, and remove it from the documentation. Then during some future refactor and in a future release I would remove the code which implements it.

from yui3.

I use update extensively, but always to set attributes so I've never run into this behavior. It's a very useful convenience, one that I'm pretty sure I lobbied for when I first started using Y.App. I'd hate to see it go.

Issues like these are exactly what made me nervous about ad-hoc attributes in the first place. Passing an object in & having some things be attributes & some not (but only at construction time) depending on the contents of a protected static array isn't terribly intuitive.

I vote option 1

from yui3.

I vote for option 4. update adds unnecessary magic.

Agreed.

from yui3.