liquidvotingio / liquidvotingio/api
Code Climate
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 17
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
I have the impression the api code is getting complex enough where a suite of code analysis like [Code Climate](https://codeclimate.com/) might begin to be useful.
Their Quality product has a free tier for open source projects.
Having test coverage (#165) and code quality stats can help developers who are prospecting liquidvoting.io to get some sense of code maturity.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Review the Elixir API repository and Code Climate Quality documentation first, then determine the required project integration; done means the open-source project reports code quality statistics alongside its test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100