untangled-web/untangled-cookbook

A set of projects demonstrating specific recipes for constructing applications.

Untangled Cookbook

This cookbook is intended to cover use-cases of how to do common tasks for single-page webapps using the Untangled Web Framework.

The recipes themselves are in the recipes subdirectory, and each has a recipe README.md. This document acts as an index of them.

Each of them is set up for use in IntelliJ, emacs, or vim. They can also be started from a plain command line.

PLEASE ADD/VOTE FOR THE TOPICS BELOW VIA THIS LINK

Running Recipes

Each recipe has a project file. You can run them in the environment of your choice. The basic idea is to use a plain clojure main REPL for figwheel, and any kind of REPL for the server. The servers in the full-stack recipes are pre-configured to appear at port 8080. No need to create a config file separately.

Running Figwheel:

lein run -m clojure.main script/figwheel.clj

If the recipe has only a UI, then browse to: http://localhost:3449. If the recipe is full-stack, continue to the next section.

Running the server:

lein run -m clojure.main
user> (go)

You should now be able to see the app at: http://localhost:8080.

Recipes

UI

• Managing lists of data
• Using InitialAppState protocol to build starting application state
• Create a tabbed interface. Includes how to lazy-load initial tab content
• Using component local state
• Use om-css to create co-located CSS for reusable styled components

Security

• Server-side security for UI-generated queries
• Integrate OAuth/OpenID for authentication

Full-stack Interactions

• Error Handling
• Background parallel queries
• Run a load from within a mutation (see Paginate a very large list)
• Showing visible indicators while lazy loads are in progress
• Some sample uses of the general load function
• Return a value from a mutation
• Modify/examine headers/cookies on a network request
• Generate a new entity (UI/Server)
• Cache invalidation
• Update data on the server
• Delete an item (UI/server)
• Add autocompletion to a form field
• Reject a transaction on the server and handle that on the client
• Paginate a very large list (with lazy loading)

Server push

• Using websockets for all network traffic

Server-side

• Server-side security for UI-generated queries
• Create and integrate a custom server component
• Add a Server Route that generates an image.
• Using SQL on the Server
• Add a Ring handler in front of API processing
• Add a Ring handler after the processing chain