Okay, that confirms my guess that parsing is isolated per file, then what about simplifying this to per-file convention-based pseudo-privacy? As I mentioned, a way to indicate that members starting with underscore are to be perceived private, and: - they should be used at least once within same module/class (e.g. no-unused-private-methods) - they should not be referenced outside of current module/class (e.g. no-privacy-violation)
Sounds simple enough and for that application it should be fine -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
