Skip to content

Configuration - decide fate and form of 'Category' #10314

@JanKrivanek

Description

@JanKrivanek

Blocked by #9823 (that item will decide the fate and possibly resolve this)

Context

Initial proposal of BuildAnalyzerRule has a Category field:

/// <summary>
/// TODO: We might turn this into enum, or just remove this.
/// </summary>
public string Category { get; }

However it was not yet decided how that will be used and if that should be a freeform text or fixed enum.

Goals

  • Decide whether we should bring back the Category and what would be the usage for the field (e.g. mass-configuration of rules by customer, or improved UX)
  • If decided that it's needed:
    • Document the usage and expected configuration by custom Checks authors
    • Reintroduce to code

Possibly related

#9823

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions