glot.io | DEPRECATED : Pastebin clone built with AngularJS and CouchDB

You likely want to process the response as JSON. Try:

Async/Await is a synthetic sugar for Promises

Your code states: const saveMultiple = async(...

An Async function will always return a Promise. (see refs below)

Your try/catch doesnt take affect in:

You can try this:

Say that you have your es4x application and a package.json, when you execute:

Try like this once::

You need an instance WeatherT m => WeatherT (MockCounter m) which just lifts a WeatherT m instance through MockCounter m thanks to the fact that MockCounter is a monad transformer. (The point of the default methods you wrote is to define such instances.)

To avoid orphan instances, one way is to separate Weather and Counter each into Class and Trans modules. Class don't need to depend on each other, while each Trans module may depend on all the Class modules (the other way around is also possible, and is in fact how mtl does it, but IMO Trans depending on Class is better: Class defines the interface, and Trans the implementation).

This is indeed a (known) problem because if you have n transformers and m classes, you potentially need n*m lifting instances. One solution is to define a polymorphic overlappable instance for all transformers (MonadTrans t, WeatherT m) => WeatherT (t m). Overlapping instances are often frowned upon but I'm not sure what actual problems there are in this case.

By the way, following the naming convention from mtl and transformers we would have MonadWeather and MonadCounter classes, and WeatherT and CounterT types (monad Transformers).

To work with IQueryable, you need to pass expression trees (Expression<...>>).

The expression tree encodes the content of the lambda at runtime, allowing it to be translated to SQL.

There are several things going on here. First of all, the signature of the trait_mod looks to be wrong. Secondly, there appears to be a bad interaction when the name of a trait is the same as an existing role. I believe this should be an NYI exception, but apparently it either goes wrong in parsing, or it goes wrong in trying to produce the error message.

Anyways, I think this is what you want:

This doesn't make sense. You have instance properties you want to examine, but React components are passed around as constructor functions and you definitely should not be reaching into the class instances from the outside to query the instantiations' properties or methods.

The code as written just isn't factored properly. React is going to instantiate the class after you've attempted to read shouldRenderInAppLayout. You need some wrapping object to represent the flag and the thing-to-possibly-render.