Skip to content

Reduce global scope pollution #3

@kerrishotts

Description

@kerrishotts

I see a lot of global variables that could easily collide with other variables. For example, v$, tempDevice, typeProject, etc.

Suggest tighter encapsulation so that these don't leak to the global scope. Getters and setters can be used as necessary to control visibility and whether or not they should/can be changed.

For v$ and other utility methods and objects, I'd suggest moving to a module system (like CommonJS, AMD, etc) so that they don't need to exist globally.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions