Write a wiki guid on how to use Dapper #688

Closed
opened 2026-05-01 20:07:22 +00:00 by a22erigr · 6 comments
Collaborator

We should write a wiki page describing.

  • What Dapper is.
  • Why use it?
  • How do you use it.
    • How do you map results.
    • How can you map custom made models.
    • How should you do when the query returns multiple rows.
  • Dapper supports multiple different Querying versions. Querying Data With Dapper.
    • Explain the different query versions.
      • When should you use them?
      • How do you use them?
      • What data is returned?

learndapper

We should write a wiki page describing. + What Dapper is. + Why use it? + How do you use it. + How do you map results. + How can you map custom made models. + How should you do when the query returns multiple rows. + Dapper supports multiple different Querying versions. [Querying Data With Dapper](https://www.learndapper.com/dapper-query). + Explain the different query versions. + When should you use them? + How do you use them? + What data is returned? [learndapper](https://www.learndapper.com/)
Collaborator
https://git.webug.se/Andras/BoundlessFlowCampus2K/wiki/Dapper
Collaborator

Review on #688

Whats done

Written a wikipage about dapper; what it is, why and how to use it.

Inspected following

  • Indentation/styling
    • Good layout
    • Maybe make introduction a bigger header containing the why, when and how headers.
  • Headers
    • "Mapping results:" and "Async methods:", uses a colon while the other headers do not.
    • Could make a bigger header called "Mapping" for the following headers: mapping results, mapping custom models and handling multiple rows
  • Comments
    • A lot of examples, which is good. Makes it way easier to understand.
    • The wikipage includes errors that can occur and why they occur, which is good.
  • General code quality
    • The page looks very nice.
    • Contains a lot of useful information.

What needs to be done

  • Mapping headers
    • Make sure that "Mapping results" does not have the colon
    • Possibly make a bigger header that contains all the other mapping headers.
  • Async methods
    • Remove the colon here as well
  • Introduction
    • Make it a bigger header containing the why, when and how headers.

Conclusion

  • A good wikipage that contains all information needed regarding dapper!
# Review on #688 ## Whats done Written a wikipage about dapper; what it is, why and how to use it. ### Inspected following + Indentation/styling + Good layout + Maybe make introduction a bigger header containing the why, when and how headers. + Headers + "Mapping results:" and "Async methods:", uses a colon while the other headers do not. + Could make a bigger header called "Mapping" for the following headers: mapping results, mapping custom models and handling multiple rows + Comments + A lot of examples, which is good. Makes it way easier to understand. + The wikipage includes errors that can occur and why they occur, which is good. + General code quality + The page looks very nice. + Contains a lot of useful information. ## What needs to be done + Mapping headers + Make sure that "Mapping results" does not have the colon + Possibly make a bigger header that contains all the other mapping headers. - Async methods - Remove the colon here as well - Introduction - Make it a bigger header containing the why, when and how headers. ## Conclusion + A good wikipage that contains all information needed regarding dapper!
Author
Collaborator

@a24nedka Can you fix the suggestions

@a24nedka Can you fix the suggestions
Collaborator

@a22erigr Yes , will fix the suggestions now!

@a22erigr Yes , will fix the suggestions now!
Collaborator

Removed colons where it was mentioned, Mapping results does not have colons anymore, and made a bigger header "Mapper" that contains other mapping headers.

Removed colons where it was mentioned, Mapping results does not have colons anymore, and made a bigger header "Mapper" that contains other mapping headers.
Author
Collaborator

Looks good to me. Can now be closed

Looks good to me. Can now be closed
Sign in to join this conversation.
No milestone
No project
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#688
No description provided.