A consistent case pattern

Open
  • Is something wrong?
#121 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
julia
Domain
data-visualization

Research direction

Start by inspecting ColorSchemes.jl and the colorschemes dict to inventory the existing naming patterns and aliases. Confirm a single normalized naming convention, apply it consistently, and preserve backward-compatible aliases in the dict. Done means the naming scheme is consistent without breaking existing names.

Written by the indexing model from the issue text.

Description

I find that often I need to remember not just a colour scheme, but also the naming scheme it uses.
Currently, ColorSchemes.jl has a mix of:

  • nocase (e.g. twelvebitrainbow, redgreensplit, gnuplot2)
  • snake_case (e.g. tableau_superfishel_stone, seaborn_dark6)
  • Camel_Snake (e.g. Spectral_10)
  • CamelCase (e.g. Zissou1Continuous)

I think it would be rather good if the format could be normalised, so there's less that needs to be remembered. Aliases for backward-compatibility can be easily added to the colorschemes dict.

Dominant language
Julia
Stars
268
Forks
44
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 JuliaGraphics/ColorSchemes.jl

All issues in JuliaGraphics/ColorSchemes.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.