ColorKeyword.fs issues
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 860
- Forks
- 99
- Avg merge
- 22m
- Merged PRs (30d)
- 1
Description
Description
There are some colour keywords in Plotly.NET/CommonAbstractions/ColorKeyword.fs that I think are slightly wrong, in relation to how they are here: https://www.w3schools.com/colors/colors_names.asp
The list below shows: existing name – proposed name (reason for reporting).
Darkolivegreen – DarkOliveGreen (Capitalisation)
Honeydew – HoneyDew (Capitalisation)
Hotpink – HotPink (Capitalisation)
LightAalmon – LightSalmon (Spelling)
LightAeaGreen – LightSeaGreen (Spelling)
LightAkyBlue – LightSkyBlue (Spelling)
LightAlateGray – LightSlateGray (Spelling)
LightslateGrey – LightSlateGrey (Capitalisation, and repeated as LightAlateGray, and missing from ofRGB function)
Skyblue -SkyBlue (Capitalisation)
I don’t know the best way to ‘fix’ these but I thought I’d mention it.
Related information
- Plotly.NET 5.0.0
Contributor guide
No contributing guide indexed for this repository
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
Start in Plotly.NET/CommonAbstractions/ColorKeyword.fs and compare the listed colour keywords with the referenced W3Schools names. Check both the keyword definitions and the ofRGB function, then verify that capitalization and spelling are corrected, the duplicate is removed, and the missing entry is present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100