scalajs

I just came across the fact that a Show[Throwable] exists.

1. It is not wired up into import Scalaz._, one needs to import scalaz.std.java.throwable._
2. It discards the stack trace entirely.

What's going on with this? :D
Is it OK if I fix both of these (for 7.2 and 7.3)?

The .forall pattern is a great way to create an optional filter for a field that could be defined or not:

case class Person(name: String, age: Int)
val nameOpt: Option[String] = Some("Joe")
run { query[Person].filter(p => lift(nameOpt).forall(_ == p.name)) }
// SELECT p.name, p.age FROM Person p WHERE ? IS NULL OR ? = p.name
// (i.e. when nameOpt := None then the `WHERE ? IS NULL`

A such question have been raised again: https://stackoverflow.com/q/56132229/10793449

We should clarify an using an arbitrary scala code as an attribute value.

Since we have all variant playable offline it would be nice to have the same help pages the website has but embedded in the app to be seen offline.

Help would be accessible from offline games menus and displayed in a modal window (like the one for the tournament FAQ).

The latest version (5.1.x) of React Router come with functional Hooks

Suggested on Telegram.

It may be easier to understand the examples if they don't show both distage and BIO at the same time, so we may want to have a variant of distage-example that uses just distage alone, using a monomorphic effect type everywhere.

• 2 Udash apps should work just fine in a single JVM
• the API is pretty ugly and even the docs suggest wrapping it

withUpActions feels odd, I'm expecting onClick. The reason it's not called onClick is that you do not run arbitrary commands as a result, instead you always emit an event.

Proposals welcome.