hagenburger / pimd

PIMD – Processing Instructions for Markdown
https://hagenburger.github.io/pimd-docs/
MIT License
20 stars 5 forks source link

ID plugin #4

Closed violetadev closed 6 years ago

violetadev commented 6 years ago

Introduce ID plugin This closes #2

violetadev commented 6 years ago

I'm getting this message when I try to run lint, any ideas what could it be? Gracias :)

$ npm run lint

> pimd@0.1.0 lint C:\Users\Violeta\dev\living\pimd
> eslint .

ESLint configuration in C:\Users\Violeta\dev\living\pimd\plugins\classes\.eslintrc is invalid:
        - Unexpected top-level property "0".

Error: ESLint configuration in C:\Users\Violeta\dev\living\pimd\plugins\classes\.eslintrc is invalid:
        - Unexpected top-level property "0".

    at validateConfigSchema (C:\Users\Violeta\dev\living\pimd\node_modules\eslint\lib\config\config-validator.js:221:15)
    at Object.validate (C:\Users\Violeta\dev\living\pimd\node_modules\eslint\lib\config\config-validator.js:238:5)
    at loadFromDisk (C:\Users\Violeta\dev\living\pimd\node_modules\eslint\lib\config\config-file.js:516:19)
    at Object.load (C:\Users\Violeta\dev\living\pimd\node_modules\eslint\lib\config\config-file.js:559:20)
    at Config.getLocalConfigHierarchy (C:\Users\Violeta\dev\living\pimd\node_modules\eslint\lib\config.js:227:44)
    at Config.getConfigHierarchy (C:\Users\Violeta\dev\living\pimd\node_modules\eslint\lib\config.js:179:43)
    at Config.getConfigVector (C:\Users\Violeta\dev\living\pimd\node_modules\eslint\lib\config.js:286:21)
    at Config.getConfig (C:\Users\Violeta\dev\living\pimd\node_modules\eslint\lib\config.js:329:29)
    at processText (C:\Users\Violeta\dev\living\pimd\node_modules\eslint\lib\cli-engine.js:163:33)
    at processFile (C:\Users\Violeta\dev\living\pimd\node_modules\eslint\lib\cli-engine.js:224:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! pimd@0.1.0 lint: `eslint .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the pimd@0.1.0 lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Violeta\AppData\Roaming\npm-cache\_logs\2018-07-30T18_56_06_126Z-debug.log
hagenburger commented 6 years ago

Thanks for your updates! I’ll have a look later. There seems to be a misconfiguration in Hound CI, it raises too many errors. I’ll check this.

hagenburger commented 6 years ago

@artnerdnet @dianavile: I’m closing this and ask you to open the pull request again. I’m going to send you the details via Slack.

benevbright commented 6 years ago

@artnerdnet I requested PR that fixes lint error. #11