🚀
ShipClojure
  • README
  • Development
    • Getting Started
    • REPL Workflow
    • AI Development with ShipClojure
    • Getting Updates
    • Formatting code
    • ShipClojure Guiding Principles
  • Backend
    • Migrations
    • Secrets
    • Routing
    • ShipClojure Blog
    • Email
  • Frontend
    • UIx + re-frame
    • HTTP Requests with Re-frame
    • Frontend Navigation with Re-frame
    • Toast Notifications
    • Icons
  • Server Side Rendering
    • Static/Landing pages
  • Auth
    • How Auth works
    • Oauth2 providers
  • Deployment
    • Deployment
  • Decisions
    • 001 - Cookie Sessions
    • 002 - Single Page Application Architecture
    • 003 - Re-frame instead of Refx
    • 003 - Move from cookie sessions to JWT Access + refresh tokens
Powered by GitBook
On this page
  • Context
  • Decision
  • Consequences
  1. Decisions

003 - Re-frame instead of Refx

Previous002 - Single Page Application ArchitectureNext003 - Move from cookie sessions to JWT Access + refresh tokens

Last updated 1 month ago

Date: 2024-10-14

Status: accepted

Context

is a reimplementation of without the dependency on . This is useful since it would take out some of the bundle size for the application.

Problems:

  • Refx is still in alpha state so there might be problems within the implementation.

  • There is little community around it and therefore not that many debug tools

  • Incompatibility with existent tools from re-frame ()

Decision

Even if ShipClojure uses as a rendering agent instead of reagent, it will use re-frame and not refx due to bigger community support.

Consequences

  • The final bundle size will be bigger due to the added reagent dependency

  • Debug and re-frame tools can be added easily to shipclojure

refx
re-frame
reagent
re-frisk
UIx