Permit color and legend customization

[dschwen]

Closes #291

[dschwen]

Ok, I see, I need to import phase_legend. Is that the best design I can do, repeatedly specifying the same default value at all levels?

[codecov]

Codecov Report

Merging #292 (0175a9e) into develop (8ed33ba) will increase coverage by 0.04%.
The diff coverage is 71.42%.

@@             Coverage Diff             @@
##           develop     #292      +/-   ##
===========================================
+ Coverage    86.73%   86.77%   +0.04%     
===========================================
  Files           46       46              
  Lines         4462     4461       -1     
===========================================
+ Hits          3870     3871       +1     
+ Misses         592      590       -2     

Impacted Files	Coverage Δ
pycalphad/plot/binary/plot.py	21.21% <50.00%> (+2.46%)	⬆️
pycalphad/plot/eqplot.py	69.89% <50.00%> (+1.47%)	⬆️
pycalphad/plot/binary/zpf_boundary_sets.py	87.25% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8ed33ba...0175a9e. Read the comment docs.

[dschwen]

Looks to me that the failed code coverage test complains about lines that weren't tested before either. :-/

[bocklund]

Thanks @dschwen! These changes go a long way in allowing users to customize the look and feel of their phase diagrams. I made a few smalls changes to the docstrings to better match how matplotlib describes their colors API (e.g. you could use this to provide any valid MPL color as a tieline_color, not just RGBA values) and I made the tieline_color arguments immutable tuples instead of mutable lists.

I'm not worried about the codecov/patch check failing. Our test suite just has some small integration tests over the plotting API, since it's more difficult to test the correctness of the graphics produced.