Brief descriptions of the auxiliary projects
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Dapper.EntityFramework
Dapper.EntityFramework.StrongName
(and the others)
why do these exist? A brief description about why they might be needed would help.
For example, I was able to gather, after reading the code for Dapper.EntityFramework, is that its there to help deal with two types present in EntityFramework: DbGeometry and DbGeography
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 reviewing the Dapper.EntityFramework and Dapper.EntityFramework.StrongName projects, then inspect the other auxiliary projects mentioned in the issue. Document briefly why each exists and when it may be needed, including the EntityFramework DbGeometry and DbGeography use case identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100