Last 12 weeks · 13 commits
4 of 6 standards met
We are currently using CubeJs to run and maintain Data Models and run a semantic layer for the data analytics in production env. We are adding eslint for the JS files used in the applications, and it seems the applications seems to have it's own set of global variables. It would be nice to include those in the config specific for cube.
While investigating why eslint wouldn't pick up the globals, I noticed eslint does not use builtin like I previously assumed. I'd like to propose to copy any globals missing in either , , but present in to one of those respective environments. Afterwards, I'd copy back any potential globals from the categories to so that it ends up containing all globals from those categories. Alternatively, could be generated dynamically in , I think actually, that'd be my preference to avoid future inconsistency.
Hey, since the globals package is commonly used by linters (eslint, standard) to set up global variables for particular environment, I thought that it would be nice to add support for the flow type system. This PR creates environment and adds the following globals: events: https://flow.org/en/docs/react/events/ utility types: https://flow.org/en/docs/types/utilities/
Repository: sindresorhus/globals. Description: Global identifiers from different JavaScript environments Stars: 606, Forks: 134. Primary language: JavaScript. Languages: JavaScript (97.6%), HTML (1.9%), TypeScript (0.3%), Makefile (0.2%). License: MIT. Latest release: v17.11.0 (1w ago). Open PRs: 1, open issues: 8. Last activity: 2d ago. Community health: 85%. Top contributors: sindresorhus, fisker, github-actions[bot], nzakas, es128, silverwind, kevva, valorkin, johanbrook, mysticatea and others.