PrismJS / PrismJS/prism

[CSharp] Attributes following comments are either mis-tagged or not tagged as `class-name`

Open
#3,799 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

language-definitions
Dominant language
JavaScript
Stars
13k
Forks
1.4k
Avg merge
15h 36m
Merged PRs (30d)
3

Description

Information

  • Language: C# (csharp)
  • Plugins: prism-csharp.js

Description
Attributes are only correctly identified when not immediately following a comment.

Code snippet

Test page

The code being highlighted incorrectly.
class MyClass
{
  /// <summary>
  /// This is a doc comment
  /// </summary>
  [Attribute]
  public string MyString { get; set; }
  
  /// <summary>
  /// This is a doc comment
  /// </summary>
  [Attribute(argument)]
  public string MyString { get; set; }
  
  // This is a normal comment
  [Attribute]
  public string MyString { get; set; }
  
  // This is without a comment:
  
  [Attribute]
  public string MyString { get; set; }
  
  [Attribute(argument)]
  public string MyString { get; set; }
}

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.

Research direction

Start with the prism-csharp.js plugin and reproduce the examples in the linked Prism test page. Compare attribute highlighting when it follows documentation comments, normal comments, or no comment. Done means each shown Attribute and Attribute(argument) is correctly tagged as class-name in all listed cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, javascript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.