You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually, for web applications with NODEJS, developers create a folder structure like this:
app\ ===> which is the root folder for NODEJS source
app\public\ ===> which is the root folder for front-end source
and JSHINT config file for each of these projects is different.
It would be great to be able to set different tools and different configs for each of these projects.
One solution could be let the user put ".lintrc" file in any folder, and that folder will be the root of a project with specific config.
The text was updated successfully, but these errors were encountered:
Sounds like an interesting idea. I am concerned with the complexity it could introduce though. Most tools require a separate execution for each configuration file used. This combined with configuration files at arbitrary depths introduces complexity in both finding the configuration files, running the tools multiple times and collating the results.
I think for now I have only one solution:
Running two different lintreview service at the same time and instead of putting .litrc in the root of the repository, I should set different LINTRC_DEFAULTS in the settings.py of each of these services.
Is it right?
Usually, for web applications with NODEJS, developers create a folder structure like this:
app\ ===> which is the root folder for NODEJS source
app\public\ ===> which is the root folder for front-end source
and JSHINT config file for each of these projects is different.
It would be great to be able to set different tools and different configs for each of these projects.
One solution could be let the user put ".lintrc" file in any folder, and that folder will be the root of a project with specific config.
The text was updated successfully, but these errors were encountered: