Choosing where to store state

Subscribe to a paid plan to get instant access to this course.

Video time: 15m35s

PREVIOUS

NEXT

Want this course?

Choosing where to store state

Updated July 11, 2018

There are four places Re-frame allows to store state in. We go over a framework of three criteria to decide where to put it.

Next Lesson:

Naming Events and Subscriptions

How do we name our Events and Subscriptions so that the names won't go out of date? We go over the guidelines with an example.

Understanding Re-frame

0 / 37

0 / 37

Re-frame Stack Overview

Reagent components

Basic HTML with Hiccup

Hiccup true, false, and nil Attributes

Hiccup Style Attributes

Hiccup class Pattern

Hiccup id and class Shortcuts

Hiccup Nested Tag Shortcut

Hiccup and subcomponents

Hiccup lists, keys, and laziness

Accessing DOM nodes

Form component best practices

Component Re-rendering

Embedding strings of HTML

Embedding Native JS React Components

Re-frame flow overview

Dispatching Events

Handling Events

Effect Handlers

Interceptors overview

Interceptor example

HTML DB Isolation

Reactive Subscriptions

Reactive Subscriptions walkthrough

Choosing where to store state

Naming Events and Subscriptions

Initialization recommendations

Deeply nested databases

Keep Events and Subscriptions Together

Calculations in Subscriptions

Indexed Entities

Indexed Entity Order