I’m getting this weird behavior using fulcro spec in the browser. I have a test that is showing in the spec UI (with no tags like :focused) and when I change the test the defines the mutations (not the test file), my spec disappears from the fulcro UI. I start changing the test file and the spec comes back green.

@pvillegas12 make sure you’re on the latest version. I tried to fix that, but am not sure why it happens

I’ve seen it as well, but I don’t really have a clue…is the console saying anything?

like a React exception caused it to not render?

It warns about the Root render taking too long

50ms-54ms

@tony.kay still getting the same behavior after updating :thinking_face:

this happens when I save the file that defines the function under test

yeah, that warning is nothing.

I had never seen it before I started using shadow-cljs…you using that as well?

@pvillegas12

could be some order-dependent thing in the code that shadow does diff than figwheel

hi is any built in http request support in fulcro? what is need is just read …/VERSION file and output it somewhere

or should I use http from Google Closure?

@kirill.salykin There is the network and you have http://book.fulcrologic.com/#_request_middleware the request/response MW think you could just add a new remote with MW that does that request for you, but seems like a bit of work if that's you're only use-case. The network part seem like the only abstraction for http and it uses xhrio directly https://github.com/fulcrologic/fulcro/blob/develop/src/main/fulcro/client/network.cljc#L306

i see, thanks!

it is indeed to much overhead with MW

closure if you’re just trying to do some side-band thing one-off

Yep, did it this way. Thanks )

As anyone worked with rdflib.js in fulcro, or any sort of parallel client-side store similar to the rdf graph in that library? Would you want to treat that as a remote?

I think that the correct way to do this long-term would be to use something like a SPARQL client / apache jena server-side and go through the normal fulcro flow, but wanted to know if anyone had ideas for a client-side only solution since that would be faster / simpler for a lunch and learn.

@devo pathom has some of these properties, it can run on JVM or Browser and supports parallel processing of the queries, its not RDF, I'm taking a look at the library and seems that pathom connect feature shares some ideas about data linkage, but the implementation is something different https://github.com/wilkerlucio/pathom

the parallel parser is not documented yet (coming soon) but the code is been used in prod for some time, if you follow the pathom docs the configuration is similar to async-parser, please let me know if you want to try it out

I never got to do some proper research on RDF, could you please tell me what you looking for on it? how it is used? is it like a thing that composes over distributed data graphs?

currently doing a lunch and learn over the SOLID protocol, which is built on RDF, so pretty new to it as well 🙂. The idea is that RDF formats like Turtle or JSON-LD store relationships in triples and are hosted arbitrarily (e.g. https://devereux.solid.community/profile/card#me). You can then use xml describing relationships to query information across those files (e.g. my friends using ). The existing library is both a web client and a store that fetches remote documents and loads them + their relationships into a client side store for later querying.

@devo for a lunch and learn you could use Datascript to simulate a datomic back-end and a pathom parser as the “remote”

all in a browser

not sure what you’re trying to teach

Mostly to show off SOLID, but wanted to do it with fulcro just to get some more experience with the framework.

ok, so since the concept is that you have distributed data stores that all have separate ownership and such, you could set up multiple datascript databases in the browser, and one pathom parser that can resolve to them in a unified query sense (e.g. Fulcro would be unaware that they were federated)

the client-side async pathom parser can do any async kinds of processing, so you could also have it hit a bunch of different real network endpoints

depends on what level of simulation your trying to do

I’m not sure if any of that is relevant, now that I look at some of the introduction stuff on SOLID

this is the solid you are talking about? https://github.com/solid/solid

yep!

@devo I don’t really know of anything that is likely to serve your specific lunch-and-learn criteria…seems like using node for a server might be the best you can do, but you could host a single server that everyone could hit, perhaps?

@tony.kay slightly off-topic question but do you know how to evaluate forms in the clojurescript repl with Cursive? The normal command (eval in REPL) spits “Cannot load ClojureScript form into Clojure repl”

@hmaurer You need to start a clojurescript repl first

@johnny I’ve one running I think, with figwheel

Which in my experience is a separate thing in cursive

script/figwheel.clj from Fulcro’s lein template

(require '[user :refer [start-figwheel]])
(start-figwheel)

Got the same thing with this as content

ooh I just realised there is a small dropdown at the top of the repl with “clj” and “cljs” as selections

I switched it to “cljs”

it works now

:face_with_rolling_eyes:

strange it didn’t auto-switch…it usually does

Ye never seen that issue

What are people using for cljs builds, Shadow or Figwheel (& the rest)?

I’m using shadow-cljs on many different projects (3 commercial). A lot of my older OSS work is on figwheel (as it helps ensure I don’t break users that use figwheel), but I prefer shadow-cljs.

- better responsiveness from the maintainer - better integration with js ecosystem - better caching and cache invalidation (I almost never have to “clean” compiled stuff)

almost? 😛

I’ve had to clear .shadow-cljs on a few upgrades

so, pretty rare

@tony.kay do you have a sample project with shadow? The book uses the Kevin template iirc

lein new fulcro app shadow-cljs

it would be the default instead of figwheel, but I have not had time to rewrite the dev guide

oh, easy-peasy! thanks

I have to say that I’m a bit confused on how to structure things and get a clojure & a clojurescript repl. Worked on a Clojure / React project before, so never “had” to deal with ClojureScript much

I’m bike shedding a lot on docker-compose related things at the moment …

Thanks for the direction

With ui routing I have a top level function nav-to! similar to the one defined in the fulcro template. I’m having trouble composing this call (which ends up calling prim/transact!) and other mutations. Say I want to change the state and navigate to another URL. Is the correct way to do this is making a mutation that calls nav-to! within it? This would nest transact! calls which I read were not desired

@kardan I recommend using IntelliJ community edition with Cursive…both are free to use for tinkering, and both are reasonably priced for real work. Then use the shadow-cljs version of the lein template…the README it generates should get you going.

@tony.kay bringing the discussion here as it might be relevant to other people trying the shadow-cljs template. Moving the devcards dependency to :dependencies in the project file (instead of under :profiles :cljs :dependencies) seems to have fixed the issue for me

Ah wait, I just realised it might have been much stupider than this. Checking the cljs profile in Leiningen Projects > Profiles seems to be enough

ah yes, it has to be visible on deps 🙂

forgot about that bit

By any chance, would you know where Cursive stores the Resolve as... settings?

I looked in the .idea directory but couldn’t find them

(to know if it’s per-project and will get commited to git)

probably ~/Library on a mac…once resolved they are global

Yet another question… Has anyone done “query whitelisting” with Fulcro? i.e. list all the queries that the application might run, store those on the server and only accept queries in that set

(for production)

“persisted queries” is the term used in the graphql land I believe

I prefer to set permissions on edges of the graph

i.e. indicate, via authorization, which edges of the graph a user is allowed to traverse (and which scalars they can read)…then you can easily look at the query (reduce the keys to a set) to see if there are any “disallowed” keys in the query

that doesn’t interfere with graph query flexibility, but gives you the security

you also need to check the “root set” of their incoming request, of course. “Can I start here?”

Namespaces on keywords gives you a nice way of resolving ambiguity that arises from context

but the root set is usually required to make it work right, even with that (e.g. ensuring you don’t walk to another user through edges is easy, but the protections on :user/address might say it’s ok to read…assuring that they don’t start (and cannot traverse through edges) can prevent that.

quick question. I'm getting my backend wired up with pathom (backed by datomic and some other stuff). in say datomic, I use 'discriminator' ID's :person/id, etc. The client, like say datomic uses :db/id by default. What's the best way to map/translate between the two? Presumably I can override ;db/id on the client, but that seems like it would get messy. And I guess my queries server mutations could do the mapping on the server. Just trying to figure out what makes the most sense.

you’re going to have :db/id no matter what. Add a UUID column for :person/id, which is unique-identity

that way you can still use tempids on :db/id (to detect optimistic results), but pathom will work well because queries can distinguish on discriminator IDs

then normalize in the ui on your disc. IDs

elogic.client/app
=> nil
(deref elogic.client/app)
=> nil
(keys (deref elogic.client/app))
=>
(:initial-state
 :mutation-merge
 :started-callback
 :remotes
 :networking
 :send-queues
 :response-channels
 :reconciler
 :read-local
 :query-interpreter
 :mounted?
 :reconciler-options
 :lifecycle
 :parser)

I seem to recall you saying this could occur when the payload was too big?

if you want to see the app state value, don’t do it that way…first, you should use Fulcro Inspect chrome plugin…but if you want to play with app state at a REPL, use (prim/app-state (:reconciler @app-atom))…and that itself is an atom

Depending on the REPL/build system you’re using, it is possible to overflow the message size and see weird things…I used to cause it in Figwheel, but I no longer dump large things in the REPL, and have not seen that issue in a long time personally