Yes. That’s bad for two reasons: 1. You could end up with conflicts between two different packages. (unless I’m misunderstanding you) 2. Polluting the global object is really frowned on. We should have as few globals as possible.
I’m not sure what the internal classes should become though. On Nov 16, 2015, at 9:53 AM, Alex Harui <aha...@adobe.com> wrote: > In JS, SomeHelperClass gets > defined on the global object. I’m wondering if that’s bad and we should > ban internal classes in FlexJS?
