search

flaviostutz / monolint

Linter for monorepos. Checks folder structure, module contents, file contents and naming conventions
MIT License
7 stars 4 forks source link

VSCode plugin #12

Open sergioflores-j opened 1 year ago

sergioflores-j commented 1 year ago

Would be nice to have a vsc plugin to run this utility as ESLint does.

Highlight the file with issues (package.json, serverless.yml, etc..)

flaviostutz commented 1 year ago

That's a really nice one! ❤️

sergioflores-j commented 1 year ago

Would you mind if I take this one to implement?

Taking a look at VSCode docs, it looks like to me that we're gonna need a new repository to build the extension. https://code.visualstudio.com/api/get-started/extension-anatomy

And ESLint as an example (perhaps an overkill example for now haha): https://github.com/microsoft/vscode-eslint

Or perhaps we could transform this repo into a monorepo as well!

What are your thoughts?

flaviostutz commented 1 year ago

Good one! Maybe it would be good for you to take at least a simple task before going full on this one just to warm a little so we can check also if the basis is good enough, what do you think?

sergioflores-j commented 1 year ago

Sounds good! which one do you suggest?

flaviostutz commented 1 year ago

I think this is a good one: https://github.com/flaviostutz/monolint/issues/2

flaviostutz commented 1 year ago

I am working now in this one (https://github.com/flaviostutz/monolint/issues/24) which I guess is the last one for the initial "core" structure, which you would probably use for the vscode plugin also.

flaviostutz commented 1 year ago

... and yes... let's transform this into a monorepo itself and activate monolint in it! Nothing more fair 😅

Just check if VSCode plugin ecosystem doesn't prefer exclusive repos somehow (for building or releasing, don't know).