✨ Add missing theme tokens
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
The issue names no files or tests; first locate the theme-token definitions and bundled theme resources, then compare the existing Types and Variables entries with the proposed token list. Done means the requested tokens are implemented, the old entries are replaced as specified, and all bundled themes include the updated tokens.
Written by the indexing model from the issue text.
Description
Description
We currently have "Types" and "Variables" theme tokens. We should replace these two with "Types Declarations", "Type Names", "Variable Declarations", "Variable Names". There are also several more that we might add...
classNamestypeDeclarationstypeNamesvariableDeclarationsvariableNamesfunctionDeclarationsfunctionNamespropertyNamesconstantsparameterNamesmoduleNamesnamespaceNamespreprocessorMacrosenumMembersannotations
If we added these, the complete token list would look like this...
textbackgroundinsertionPointlineHighlightselectioninvisibleskeywordsclassNamestypestypeDeclarationstypeNamesattributescommandsvaluesconstantsnumbersstringscharactersvariableDeclarationsvariableNamespropertyNamesparameterNamesfunctionDeclarationsfunctionNamesmoduleNamesnamespaceNamesenumMemberspreprocessorMacrosannotationscomments
Additional Context
In Xcode, class names, function names, type names, etc. are differentiated between “Project” and “Other”. This helps developers quickly see what’s part of their project vs. an external dependency, making it easier to navigate complex projects, identify ownership of code, and make refactoring decisions. Is this something we want to implement as well?
We also need to update all of our bundled themes to include these tokens.
- Dominant language
- Swift
- Stars
- 23k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 CodeEditApp/CodeEdit
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CodeEditApp/CodeEdit#2190 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
CodeEditApp/CodeEdit#2195 · 7 reactions ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
CodeEditApp/CodeEdit#2185 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
CodeEditApp/CodeEdit#2181 ·
-
creashes on starting Openbug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
CodeEditApp/CodeEdit#2180 ·
All issues in CodeEditApp/CodeEdit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
googleapis/google-cloud-swift#1151 ·
-
`--app` focus through the daemon can pick an off-screen window and refuse with `axElementNotFound` Openclawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:other issue-rating: 🦞 diamond lobster no-stale P1
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
code health
Difficulty 1/5 Under an hour Newbie friendliness 72/100
apple/coreai-models#288 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100