DapperLib / DapperLib/Dapper.Contrib
What is the proper way to contribute to Dapper.Contrib
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 293
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
Some time ago I created a PR fixing an issue with GUID keys. The fix is simple and applies to Postgres only. But I am ready to fix the issue for all the adapters. Actually there are quite a few small issues there and I guess community is ready to fix them and make the lib better. But how should we try to do it? Is it possible in general?
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
No source file, test, or entry point is named. Start with PR #1535 and the issue's contribution-process question; define whether the outcome is contributor guidance or adapter fixes, then establish a concrete scope and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, postgresql
- Domain
- databases, developer-experience
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100