Any version of this for slim templates

[justin808]

Has anybody tried to port this to slim?

How easy would it be for this project to support both?

[sds]

It would not make sense for haml-lint to support linting Slim templates, as much of the plumbing is built specifically to deal with nuances of HAML.

I've wanted to build slim-lint for a while, but as we are still using HAML templates at Brigade I haven't been able to justify the venture just yet.

[justin808]

@sds would you use slim on a new project? The only disadvantages I see of slim are

1. no linter
2. RubyMine support is a bit buggy compared to haml

Otherwise, it seems superior.

[sds]

Yes, if given the option I would choose Slim for new projects. Its use of the Temple library was a solid design decision (given my experience diving into the HAML project's code). Granted, HAML works great as well, I just see Slim as more extensible given the framework it was built on top of.

Maybe I'll find some time to spike on a quick proof of concept to get the ball rolling. Given Temple simply returns Sexps, it should be easy to get started with.

[justin808]

@sds Sweet. You'll be popular!

[deivid-rodriguez]

👍

slim is my personal preference too, but in the last project I started I chose haml just because there's haml-lint.

slim-lint has been on my "personal project candidate list" for a while, so I'll be willing to help if this is actually started and I get some spare time.

[sds]

Circling back on this: I've thrown together a working Slim linter (creatively named slim-lint), which functions similarly to haml-lint, and is heavily based off its codebase. RuboCop integration seems to be working, but I don't have any large projects using Slim so it's hard to know if I've missed some cases and the linter is noisy. If you do have some large Slim projects, take it for a spin and let me know what you think!

[justin808]

Will do! 👍

[Vorob-Astronaut]

@sds 👍