Why are there multiple CSS classes that mean the same thing?

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
tooling

Research direction

Review the definitions and usages of the listed syntax-highlighting classes: htmlElementName, xmlName, htmlAttributeName, xmlAttribute, comment, htmlComment, string, jsonString, xmlAttributeValue, htmlAttributeValue, cssPropertyName, and jsonKey. Determine whether their distinctions are intentional; the issue is complete only after the project has a documented decision about preserving or consolidating them.

Written by the indexing model from the issue text.

Description

There's the following pairs with the same semantic meaning:

  • htmlElementName and xmlName
  • htmlAttributeName and xmlAttribute
  • comment and htmlComment
  • string, jsonString, xmlAttributeValue and htmlAttributeValue
  • cssPropertyName and jsonKey

Is there a reason these are separated out instead of just using the same class name?

Dominant language
C#
Stars
267
Forks
58
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 CommunityToolkit/ColorCode-Universal

All issues in CommunityToolkit/ColorCode-Universal

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.