dotnet/roslyn

Support more format string embedded langauges

Open

#71,973 opened on Feb 6, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (4,257 forks)batch import
Feature Requesthelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

We have requests to expand the set of embedded languages we support. While some of them are enormously large, and likely not something we'd want to ship in-roslyn itself, the following are very reasonable and would be nice and simple delighters:

From most important to least important these are:

  1. NumericFormat
  2. EnumFormat
  3. GuidFormat
  4. TimeSpanFormat
  5. DateOnlyFormat
  6. TimeOnlyFormat

It would be good to support both classification and completion for these items, just like we have for DateTimeFormat.

Contributor guide

Research direction
Study how DateTimeFormat is implemented in the Roslyn codebase for format string embedded languages. Then replicate similar logic for NumericFormat, EnumFormat, GuidFormat, TimeSpanFormat, DateOnlyFormat, and TimeOnlyFormat. Focus on classification and completion support.
Tech stack
csharp
Domain
developer experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C#Roslyn internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40