Use `mix format` (from Elixir 1.6() instead of credo

Open
#88 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
elixir
Domain
tooling

Research direction

Start with the discussion in pull request #21 and review the referenced Heroku Elixir buildpack configuration to confirm the supported Elixir version. Check how Credo is currently used in the project, then determine whether mix format can replace it. Done means formatting is handled by the built-in Mix task without breaking the supported Heroku build.

Written by the indexing model from the issue text.

Description

chore enhancement technical

see: https://github.com/dwyl/github-backup/pull/21#discussion_r174291676

Instead of using Credo we can use the build in Elixir mix command mix format https://hexdocs.pm/mix/Mix.Tasks.Format.html

However I think Heroku buildback for Elixir still use the 1.5 version so we might need to wait a bit before using 1.6
see https://github.com/HashNuke/heroku-buildpack-elixir/blob/master/elixir_buildpack.config

Dominant language
Elixir
Stars
33
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwyl/github-backup

All issues in dwyl/github-backup

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.