Question 1

How to integrate Secretary with Reagent or Re-frame?

Accepted Answer

Define routes that dispatch to Reagent components or Re-frame events. For example, in a defroute action, call (re-frame/dispatch [:set-route params]) to update the UI state based on the matched route.

Question 2

Secretary vs bidi or reitit for ClojureScript routing?

Accepted Answer

Secretary is simpler and more lightweight, ideal for basic routing with familiar syntax, while bidi and reitit offer bidirectional routing and better server-client sharing. Choose Secretary for quick setup, but opt for bidi/reitit if you need advanced features like nested routes.

Question 3

How to handle nested routes in Secretary?

Accepted Answer

Secretary doesn't support nested routes natively. You must manage hierarchy manually by defining separate routes and using parameters or context in your actions to simulate nesting, which can add complexity.

Question 4

Does Secretary work with browser history APIs?

Accepted Answer

Yes, as shown in the README example with goog.History. You can listen to navigation events and call secretary/dispatch! to sync route changes, but integration requires additional setup compared to out-of-the-box solutions.

Question 5

Can I use Secretary for server-side Clojure routing?

Accepted Answer

No, Secretary is designed specifically for client-side routing in ClojureScript. For server-side routing in Clojure, consider libraries like Compojure or Pedestal, which handle HTTP requests differently.

Question 6

How to prefix routes with a hash for older browsers?

Accepted Answer

Call (secretary/set-config! :prefix "#") to add a hash prefix to generated URIs. However, be aware that this breaks URI specification compliance, as the fragment may incorrectly hide query parameters.

Secretary

What is Secretary?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions