Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Dapper.Contrib readme documentation needs clarification about non-attributed "id"

Open Beginner friendly
  • Is something wrong?
#22 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
75/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp
Domain
documentation

Research direction

Start with the Dapper.Contrib README section containing the statement about a case-insensitive "id" property. Confirm whether an unannotated "id" behaves like [Key] or [ExplicitKey], then clarify the documentation so the database-generated versus user-generated behavior is unambiguous.

Written by the indexing model from the issue text.

Description

The documentation states:
"Dapper will automatically use a property named "id" (case-insensitive) as the key property"

However, it's not clear whether "id" is treated as a [Key] or an [ExplicitKey]. Meaning, if the attribute is not specified, is the "id" field treated as database-generated or user-generated?

Dominant language
C#
Stars
294
Forks
108
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DapperLib/Dapper.Contrib

All issues in DapperLib/Dapper.Contrib

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.