currentoor

(ns ucv.models.user
  (:require #?@(:clj  [[datomic.api :as d]
                       [ucv.util :as util :refer [spy when-clj]]]
                :cljs [[ucv.auth :as auth]
                       [ucv.util :as util :refer-macros [spy when-clj]]])
            [clojure.spec.alpha :as s]
            [taoensso.timbre :as log]
            [fulcro.client.primitives :as prim :refer [defsc]]

            [ucv.util :as util]

ah45

(ns railway-oriented-programming
  "An adaptation of [Railway Oriented Programming](rop) using the
  [Cats](cats) library in Clojure.

  [rop]: http://fsharpforfunandprofit.com/posts/recipe-part2/
  [cats]: https://github.com/funcool/cats"
  (:require [cats.builtin]
            [cats.core :as cats]
            [cats.monad.either :as either]))

benvium

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  ...
  ...
  ...

  RCTRootView *rootView = [[RCTRootView alloc] initWithBundleURL:jsCodeLocation
                                                      moduleName:@"MyAwesomeApp"
                                               initialProperties:@{}
                                                   launchOptions:launchOptions];

idibidiart

Building a Maintainable, Agile Architecture for Realtime, Transactional Apps

A maintainable application architecture requires that the UI only contain the rendering logic and execute queries and mutations against the underlying data model on the server. A maintainable architecture must not contain any logic for composing "app state" on the client as that would necessarily embed business logic in the client. App state should be persisted to the database and the client projection of it should be composed in the mid tier, and refreshed as mutations occur on the server (and after network interruption) for a highly interactive, realtime UX.

With GraphQL we are able to define an easy-to-change application-level data schema on the server that captures the types and relationships in our data, and wiring it to data sources via resolvers that leverage our db's own query language (or data-oriented, uniform service APIs) to resolve client-specified "queries" and "mutations" against the schema.

We use GraphQL to dyn