On 11/6/16, 3:19 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlosrov...@apache.org> wrote:
>Hi, > >className in flexjs translates to class. >There's as well typeNames. > >If I write a component that uses some css class (in its definition), but I >want to add some new css rule in app instantiation...what's the >recommended >way to manage this situation? > >should I override the className UIBase method? (that's the way I'm >thinking >right now to use so always reattach the basic css rules needed for the >compoenent) or maybe there's some other trick in flexjs arsenal. I think that's what typeNames is for. TypeNames should get appended to any classNames specified by the developer. Or maybe I don't understand the scenario. We could also change they way things work now. My thinking was that typeNames contained the list of class selectors that should act like type selectors. The type selector set is not extensible, so typeNames effectively allows specification of things that act like type selectors. HTH, -Alex
