Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

External Anorm integration in documentation #307

Merged
merged 1 commit into from
Mar 7, 2021
Merged

External Anorm integration in documentation #307

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 8 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,8 +58,9 @@ Integrations are available for:
13. [Quill integration](#quill)
14. [Cats integration](#cats)
15. [Doobie integration](#doobie)
16. [Benchmarking](#benchmarking)
17. [Publishing](#publishing)
16. [Anorm integration](#anorm)
17. [Benchmarking](#benchmarking)
18. [Publishing](#publishing)


## Quick start
Expand Down Expand Up @@ -1259,6 +1260,10 @@ sql"select shirt from clothes"
```
- Note that a type ascription to the `ValueEnumEntry` abstract class (eg. `ShirtSize.Small: ShirtSize`) is required when binding hardcoded `ValueEnumEntry`s

## Anorm

Anorm provides a [module to support Enum](https://playframework.github.io/anorm/AnormEnumeratum.html) as `Column` and parameters.

## Benchmarking

Benchmarking is in the unpublished `benchmarking` project. It uses JMH and you can run them in the sbt console by issuing the following command from your command line:
Expand Down Expand Up @@ -1308,4 +1313,4 @@ Should publish all needed artefacts. Note that `sbt circe-aggregate/publish-sign
Issues and PRs are more than welcome.

* For bug fixes, enhancements, version bumps etc: please feel free to send a PR or issue
* For _new_ integrations: these are generally bigger investments, and not all projects are a good fit to be maintained by me, so it would be a good idea to send an issue first to gauge interest and fit. If you feel it's a faster/better to have a concrete PR to discuss things with, by all means, feel free to go that route too.
* For _new_ integrations: these are generally bigger investments, and not all projects are a good fit to be maintained by me, so it would be a good idea to send an issue first to gauge interest and fit. If you feel it's a faster/better to have a concrete PR to discuss things with, by all means, feel free to go that route too.