Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run for subdirectories #77

Open
qqilihq opened this issue Mar 30, 2020 · 0 comments
Open

Run for subdirectories #77

qqilihq opened this issue Mar 30, 2020 · 0 comments

Comments

@qqilihq
Copy link

qqilihq commented Mar 30, 2020

First: This plugin has done a great job during the last years -- thanks for this!

We have recently restructured our repository and split it into sub-projects and during this, we have moved some configuration files to subdirectories. The structure now looks like this:

+-- subproject-a
|     +-- src
|     |     +-- pug-files
|     +-- .pug-lintrc.js
|     +-- package.json
+-- subproject-b
+-- subproject-c

Since then, the puglint plugin unfortunately no longer works for us. If I interpret the code correctly, the plugin only seems to check the root path only. (this is different to how e.g. VS Code behaves -- there I can e.g. have individual and different tsconfig.json instances for the sub projects)

The following workarounds seem to work:

  • additionally install pug-lint in the repository’s root, and add a .pug-lintrc.js there as well (our build process requires it to be present in subproject-a). To reduce duplication, I used:

    module.exports = require('./subproject-a/.pug-lintrc.js');
    
  • open subproject-a instead of the repo’s root -- this way, unfortunately we’re losing context.

Is there something I’m missing or a better fix or workaround for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant