Project Roadmap to v1.0

[rrrene]

Project Roadmap to v1.0

[Tuxified]

At "0.3.0" a Formatter API is mentioned, is that already implemented? Where can I find some clues on how to write my own formatter? I'm asking because I'd like to add Credo to CodeClimate engines, for which it needs JSON output.

[rrrene]

We do not have JSON output yet. There is also no real idea of a Formatter API I have to admit. I will have to update this issue. Thx for reporting! 👍

P.S.: There is, I think, already a CodeClimate Engine which supports Dogma and Credo. Read something about it on the Twitter, but I have not followed that project.

[Ramblurr]

Are there any plans to implement 'fixing" of format errors/warning? I'd normally call that a code formatter, but we're already using that term here.

[rrrene]

I guess you mean something like auto-correct?

I am not completely against it, but I also think that one might become pandora's box if we tackle it too soon. Pretty sure this would be a post-1.0 item ...

Any thoughts on this?

[devonestes]

Hey - happy to see a roadmap to 1.0! Thanks for taking the time to put it together.

I was just looking at the current issues and I was wondering what would be most helpful for me to jump in on next. I have a feeling the formatter API is something you'd like to tackle, but if there are any priority issues or things that you know are blockers for getting to 1.0, then just let me know and I'll chip in where I can.

[rrrene]

I am a bit torn whether or not I want JSON support "at all costs" for v1.0. It would sure be nice, but to be honest, I do not have an elegant idea how to do it, yet.

With regards to the magic v1.0 milestone, bug hunting is an equally important endeavour. 👍

[jeremyowensboggs]

What about allowing some sort of Date tag on TODO's and FIXME's? The presence of the TODO or FIXME isn't considered an issue until the date has passed?