DapperLib / DapperLib/DapperAOT
Migrate bulk of analyzers to non-generator API, and use SQL syntax from props
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 472
- Forks
- 43
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 18
Description
- we shouldn't force unnecessary work in the generator pipe, if it can be moved to a lower-tier
- incremental generators don't get access to project properties until the final "generate"; we need it earlier, during parse
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
The issue names no files, tests, or entry points; start by locating the analyzer and generator pipeline and how project properties reach parsing. Done means the bulk of analyzers uses the non-generator API, unnecessary work is moved to a lower tier, and SQL syntax from project properties is available during parsing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100