Can provide a low-level API(API before mapping entity objects)？
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Most of the time we get the object is also serialized (JSON or binary) and returned to the caller through the API, which will have an additional serialization object operation. For lists with large amounts of data, the objects created can also put pressure on the GC. If you can provide a low-level API before mapping each row of data to an object, you can customize the data returned by the query. Or an extension method can directly return the query result as a JSON string.😊This way the library becomes very powerful
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 files, entry points, or tests are named. Start by reviewing Dapper’s existing query and object-mapping APIs, then determine whether the requested low-level row access and direct JSON result are one feature or separate proposals. Done would require a concrete API scope, defined serialization behavior, and tests covering large result sets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100