Contributing

[rashfael]

Hi!
I've been using pug and vue for a long time and I'd love to contribute to getting pug to lint in vue SFCs.

I have read through existing discussions like vuejs/vue-eslint-parser#29 and played around with some code.

If I may ask, what made you go with a separate plugin and copying rules instead of integrating pug with vue-eslint-parser?

[Shinigami92]

If I may ask, what made you go with a separate plugin and copying rules instead of integrating pug with vue-eslint-parser?

1. The authors didn't want to extend it to support pug additionally to pug, because it would make double of work
2. The kind of how the lexer of pug works differentiates much from how it works of the html stuff

So right now, we need to do everything twice 🙁 one for html and one for pug
There were one try of making something to generate html out of the pug and use the html parser, but that dramatically failed and had many problems
You are loosing stuff like --fix for pug and so on. And it's even more complicated than this plugin is right now

[Shinigami92]

I will pay you 10€ if you successfully implement this rule and I can release it. That's how much the rule is worth right now.
To put in relation: I think about to pay 1-3 € per rule that I think it is worth to pay.
Some rules are too easy to implement to get payed for, but some are more complicated, because e.g. they need to access sub-scoped variables in pug code, and I currently do not have a parser or parsed out code for that embedded JS stuff right now.

Do not see it as a money per hour, because the "minimum wage" would be worth as hell 😉

[rashfael]

Thanks for the offer, but for me having a usable linter for my favorite preprocessor is payment enough.
Since this will be useful for my whole team at my employer I will probably develop this on company time anyways :D

[Shinigami92]

I could also invite you as collaborator into the repo if you are interested, you could be a co-maintainer in the long run if your PR is successful

[Shinigami92]

@rashfael Oh and as a side-note: the labels do not reflect the priority but the "kind" of what the rule is defined by eslint-plugin-vue

So go with your own defined prio, the rules that are requested by us - the community - are the ones that should be prioritized first, because that are the rules where we benefit the most from.

[rashfael]

Ah, I see, thanks for clarifying.