Static colour lint misses hex colours in .js files
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- css, javascript, python
Research direction
Start with tests/web/test_static_lint.py, which already checks hex colours in .css files and rgb(a) channels; the change is to make the same check cover .js files under the view directories. Run the test first to confirm it passes today, then check views/setup.js around lines 289-290 to see the placeholder hex values the lint will flag. Done means the lint fails on a hex colour added to a view's .js file, and passes on the existing setup.js examples via an allow-list or after moving them into data.
Written by the indexing model from the issue text.
Description
tests/web/test_static_lint.py fails on hex colours in .css files and on raw rgb(a) channels. A hex colour in a view's .js file still passes, and that colour would ignore the team palette.
The only hits today are the example input values in views/setup.js (around lines 289-290, harmless placeholders). Extend the lint to .js with an allow-list for those, or move the examples into data.
Found during the team-branding docs review (PR #42).
🤖 Generated with Claude Code
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 18h 37m
- Merged PRs (30d)
- 15
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
- 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.
More from IgniteRobotics/flashpoint
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
IgniteRobotics/flashpoint#44 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
IgniteRobotics/flashpoint#43 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
IgniteRobotics/flashpoint#12 ·
Maintainers usually reply within 1 day
-
tools/update-owlet-manifest.py ignores --help and starts downloadingMay be free again @yoveneim claimed this 11 days ago, and no pull request is open. Openbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
IgniteRobotics/flashpoint#11 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
All issues in IgniteRobotics/flashpoint
Similar issues
-
New InternshipOpennew_internship
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
get_graph warns that the oneway column is missing when no way has a oneway tagPossibly taken @HTenkanen claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cython/cython#8110 · 2 comments ·
Maintainers usually reply within 1 day
-
fix: security 🔐 style: article/section 📝 system: data-mgmt 🗃️ system: security 🔐 system: software 💻
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
uabrc/uabrc.github.io#1267 ·
-
Link Checker ReportOpenBot Type: Bug Type: Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day