skunk
sbt-tpolecat
Our great sponsors
skunk | sbt-tpolecat | |
---|---|---|
4 | 6 | |
1,549 | 371 | |
1.5% | 1.3% | |
9.2 | 7.3 | |
3 days ago | 5 days ago | |
Scala | Scala | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
skunk
-
New to Scala;
The major performance issue with Skunk is tracked here. tl;dr prepared statements currently take a horrifying number of network round-trips to the database. I'm sympathetic to Rob's "what you see is what you get" priorities for Skunk. But I'm glad to see an outline of a plan that sounds like it would satisfy those objectives without being so, for lack of a better term, naïve in their pursuit.
-
Pleasant to use Scala libraries
The same creator is working on skunk, which is very exciting. Only works for Postgres though.
-
Zio / Zionomicon : is it worth it ?
The libraries doobie and skunk are more closely associated with cats. They both use cats-effect and fs2 for implementing database connectiona and input-output operations. The doobie library is a wrapper on JDBC, and as such is compatible with many DBMS, such as MySQL, PostgreSQL, H2, Oracle... Whereas skunk is specific to PostgreSQL, and is based on using the server protocol of that database.
sbt-tpolecat
-
Scala Resurrection
I'm awed by the maturity of the Scala 2 compiler. Every minor version in the 2.13 series adds a new linting improvement. You can see that if you have sbt-tpolecat in your project. I'm always happy to see that some option from Wartremover is no longer used.
-
Why are effects better for retries than Future?
Note that this assumes that non-Unit values are silently thrown away, which you should always configure scalac, preferably via sbt-tpolecat, not to allow.
-
New to Scala;
sbt-tpolecat to automatically provide reasonable Scala compiler settings.
-
Scala and Java Upgrade strategy
Start with settings strict compiler flags if you haven't already, for instance using sbt-tpolecat. This will help you remove the most obvious warts in your codebase.
-
Which static analysis tool do you use for Scala?
However, after a while, I found that most of the things I needed were already covered by the compiler. And that Rob's (aka tpolecat) list of compiler options provided all the ones I needed for my style of coding. I Then learn that there was this sbt plugin that managed the list for me and also took care of changing the options according to the Scala version.
-
Is there a way to beautify the code after Scala 3 migration?
Sorry, have nothing useful to contribute (although I'd recommend you to set a restrictive set of scalac flags, for example from sbt-tpolecat, to let compiler help you), but just wanted to praise the Scala team and remind us of all those "Python 3 situation" rants we've saw 2 years ago and how silly they look now.
What are some alternatives?
doobie - Functional JDBC layer for Scala.
scaluzzi - Additional rules for Scalafix. The part of scalazzi rules.
doobie-quill - Integration between Doobie and Quill libraries
Scalafix - Refactoring and linting tool for Scala
zio-magic - Construct ZLayers automagically (w/ helpful compile-time errors)
scalafix-organize-imports - A CI-friendly Scalafix semantic rule for organizing imports
fly4s - A lightweight, simple and functional wrapper of Flyway using cats effect.
sbt-jni - SBT Plugin to ease working with JNI
pfps-examples - :izakaya_lantern: Standalone examples shown in the book "Practical FP in Scala: A hands-on approach"
sbt-dependency-check - SBT Plugin for OWASP DependencyCheck. Monitor your dependencies and report if there are any publicly known vulnerabilities (e.g. CVEs). :rainbow:
fs2-kafka - Functional Kafka Streams for Scala
Wartremover - Flexible Scala code linting tool