Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a roadmap #154

Closed
jevans-gp opened this issue Apr 19, 2016 · 4 comments
Closed

Provide a roadmap #154

jevans-gp opened this issue Apr 19, 2016 · 4 comments

Comments

@jevans-gp
Copy link

It'd be interesting to see a roadmap of what needs to be done to get to version 1?

@ryaneberly
Copy link
Contributor

@jevans-gp

Something like:

Version 1.0.

Got other suggestions?

@jevans-gp
Copy link
Author

I don't have suggestions, but i'd like to be able to help.

I'll take a look at Parameterisation, but i won't promise anything.

@ryaneberly
Copy link
Contributor

I'm not is 'parameterization' is the correct term for it. But instead of hardcoding the severity and the message text in code -- it is placed in the json configuration.

The resulting code is cleaner too. Just add the message code and the rest is filled in by the framework. If you review the changes made by the commit I mentioned, it should make some sense.

Just send out a PR if you want to try some. Thanks.

@ryaneberly
Copy link
Contributor

1.0.0-RC1 includes

  • correct parameterization of all plugins.
  • all plugins use the context framework.
  • rule groups are implemented
  • folder specific configuration support: .cflintrc and .cflintrc.xml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants