LINQ2DB support
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 505
- Forks
- 186
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Would it be possible to improve LINQ2DB support? I've noticed that most of my problems came from null propagation handling.
The HandleNullPropagationOptionHelper has some hardcoded namespaces for Microsoft DB libraries, are there some special conditions that need to be met to "certify" LINQ2DB to add it there?
I feel that a lot of people that have tried LINQ2DB were unable to get to the bottom of why they received errors.
I know that the workaround is to set [EnableQuery(HandleNullPropagation = HandleNullPropagationOption.False)], but it's not easy to find.
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 reading HandleNullPropagationOptionHelper and the existing hardcoded Microsoft DB library namespaces. Investigate the null propagation errors reported with LINQ2DB and determine what conditions the project uses for provider support. Done means LINQ2DB behavior and the recommended workaround are addressed in a discoverable, tested way.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100