Улучшить парсинг текста с примерами обобщения
Open
Nobody has claimed this yet.
task
- Dominant language
- C#
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
В сгенерированном .editorconfig файле можно найти такие артефакты:
This rule flags overly complex LINQ expressions, specifically expressions that call System.Linq.Enumerable.Where%60%601(System.Collections.Generic.IEnumerable{%60%600},System.Func{%60%600,System.Int32,System.Boolean}) followed by one of the following methods:
Нужно изменить генерацию таким образом, чтобы на выходе получались читаемые примеры кода с дженериками:
This rule flags overly complex LINQ expressions, specifically expressions that call Enumerable.Where<TSource>(IEnumerable<TSource>, Func<TSource,Int32,Boolean>) followed by one of the following methods:
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing generation of the .editorconfig output with the LINQ example shown in the issue, then trace the text-parsing or generation entry point that produces the encoded generic signatures. Done means the generated examples use readable generic syntax such as Enumerable.Where instead of %60 or other artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100