fmonniot / cassie Goto Github PK

It must have a real implementation, and not the current ??? placeholder we currently have :)

With the same capabilities but using IO instead of ListenableFuture.
It should also hide all those pesky blocking methods :)

As of the time of writing this issue (), CassieError is just a wrapper around a String.
We should make it more useful :)

As a starting point, here is what doobie is doing for their invariant errors:

/**
 * Module defining the type of exceptions representing unmet expectations.
 * These typically indicate a problem with the schema, with type mapping,
 * with driver compliance, and so on. The intent is that they be as fine-grained
 * as reasonable for diagnostic purposes, but it is not expected that the application
 * should be able to handle them in any meaningful way.
 */
object invariant {

  sealed abstract class InvariantViolation(msg: String) extends Exception(msg)

  sealed abstract class UnexpectedCursorPosition(msg: String)
   extends InvariantViolation(msg)

  case object UnexpectedEnd
    extends UnexpectedCursorPosition("ResultSet exhausted; more rows expected.")

  // …

}

• As a SNAPSHOT when pushed to master without a tag
• As a RELEASE when pushed to master with a tag
  • Checking that the tag and version in SBT are the same (otherwise what to do ?)

Doobie queries have a nice syntax, maybe we can do something similar with Cassie ?

As cassie is sufficiently small that all documentation can be done on the README page.

Self-explanatory

Right now, Cassie only support Tuple2. It should support all of them instead.