How to use https://github.com/PrismJS/prism with reagent? prism looks great.

@wqhhust you mean how would you use the prism library as a component in a reagent webpage?

yes, in vue, it's simple as

<template slot='action_plan' slot-scope='data'>
          <prism language="sql" :plugins="['toolbar','copy-to-clipboard']" :code="data.value">
          </prism>
        </template>

have you taken a look at https://github.com/reagent-project/reagent/blob/master/docs/InteropWithReact.md

i actually do not know vue, but i am assuming that is some kind of jsx like syntax?

do you guys generally store something in a top most atom, then have the children of the parent handle mutations?

(for something rather simple)

there are many approaches. if the project is simple, you can do it that way. note that components re-render whenever any part of an atom they reference changes, so you may find it a good practice to create cursors to the specific portion of the top-level atom. i find it helpful to keep all state mutators in a separate file and ensure that they are synchronous rather than mutating the state atom directly.

You can also keep truly local state locally instead of in the top-level atom. Once you start sharing it between components, it is probably better to put it in a central place.

@lee.justin.m my example is more like a single api call to get some data, and the various components in the app will use that same info (potentially)

api is called on initial load

what causes subsequent mutations?

actually now that I think about it, I don’t forsee any mutations on that

then you almost don’t need an SPA. it may be easier to just serve static html

but I’ll need the data at any given time

and I may have a second call where I might mutate that data before I send it back to the server

this is all a bit abstract. if you have very simple dataflow, it almost doesn’t matter how your structure. the key thing that reagent does for you is implement an observer pattern where components re-render when any part of a ratom they have dereferenced during their render function changes

if you are just loading data and then displaying it, you could just ship html from the server, which may be faster because the js overhead goes away. or you can use reagent and just stick it into a big ratom and render html client side