Ah, ok, thanks.

@tony.kay, forgive me, I don't actually think I'm following. Where do I put that? For proof of concept, I tried this:

(easy/make-fulcro-server
      :config-path config-path
      :env.edn/PORT 8000

But that doesn't seem to do anything. Is it a JVM option? Like -D:env.edn/PORT 8000?

in the config file itself 😉

{:port :env.edn/PORT}

@d4hines

so, I’d add a production.edn file into your resources, perhaps in the config folder, and that is the config path I’d give via server main.

The config reads defaults, then merges the named config on top of it.

:env/PORT reads it as a string…`:env.edn/PORT` runs it through read-string

> I mean, you already did an optimistic update, so the UI should already be correct. What is there to refresh? Well, if I call the pristine->entity* the UI reverts to the unchanged fields/undoes the changes.

did you commit them via entity->prisine* earlier? @bbss

those functions just manage local state

when you “commit to server”, you need to update your local pristine copy

pristine->entity* is UNDO

oh my, now I feel dumb..

entity is always your entity, and you’re always editing your entity. The pristine is the backup copy 🙂

Yeah I somehow missed the entity->pristine* is flipped. Sorry for the noise.

no problem 🙂

if you see something in the docs that could be clearer, feel free to send a PR

yeah, I don't think it was the docs, it's obvious now.

I'll try to contribute to the docs if I find something.

That did the trick. Thanks @tony.kay

@tony.kay so technically I should be able to drop in fulcro like so? https://gist.github.com/njj/a9f79388584adbcff525008a8fec7fae#file-project-clj-L5-L13

go with 2.4.3 on fulcro

ok

drop untangled-spec

use fulcro-spec 2.0.1-1

drop bidi, update core-async to latest

use fulcro-inspect in dev context, and use latest version (which I think is 2.0.1)

clj 1.9.0 is out 🙂

update clojurescript to 1.10.2?? whatever it is

haha yeah there are some other things that need help here for sure

if you use bidi and pushy, just update their versions to latest

ok

same with component

then do a lein deps :tree and make sure you don’t have any untangled stuff or Om Next coming in

and also good idea to resolve any warnings that gives

so fulcro-inspect isn’t 100% needed at first right?

since its a dev tool?

correct

be esp. careful about versions of guava that you get warnings about…that can break the build if it chooses an old one

@njj if you use figwheel or devcards, update those too

has anyone seen this error?

Could not Analyze resources/public/generated/js/dev/fulcro/util.cljc
No such namespace: clojure.spec.alpha, could not locate clojure/spec/alpha.cljs, clojure/spec/alpha.cljc, or Closure namespace "clojure.spec.alpha"
Please see resources/public/generated/js/dev/fulcro/util.cljc

running fulcro 2.4.4

not so bad, eh?

now port everything to defsc? 😄

I guess you got that error to go awway by upgrading Clojure?

or cleaning