@geraldodev no examples that I know of, but it was very easy to get going using https://github.com/fulcrologic/fulcro-websockets . The Readme has pretty good instructions - give it a try, and if you have any problems, I’m sure someone here can help.

I gave a talk at the conj, it’s on youtube https://youtu.be/PMbGhgVf9Do

I went down an unfortunate rabbit hole today. So maybe this will be useful to someone. Setting up a new project, I added fulcro-spec as per the fulcro-template (which happens to use kaocha, but does not include :reporter [fulcro-spec.reporters.terminal/fulcro-report] in the tests.edn config. I totally missed that in the fulcro-spec README until after I figured out the issue. The problem is, everything seemed to work except for pretty-printing of large diffs. Which meant I went down a rabbit hole of figuring out what is wrong with my kaocha config. In reality, it's this bit of code:

(defn assertion-type
  "Given a clojure.test event, return the first symbol in the expression inside (is)."
  [m]
  (if-let [s (and (seq? (:expected m)) (seq (:expected m)))]
    (first s)
    :default))

@tony.kay Just saw the RAD video! Here’s a spitball thought thread. I spent the weekend looking around the ecosystem for new and old ideas. I discovered Duct. Now I spent 2 days with duct and 10mins with your video, so I definitely don’t know everything about everything. But here a little thought: Very light summary of duct Basically Duct aims to declare your system (mainly back-end) with data. It’s a framework that generates Integrant systems, and comes with some pre-fab modules for the basic needs. The one thing I like is that the maker of Duct differentiate’s between modules and components, where a component is what you’d expect (a router, db, webserver), but a module can generate and manipulate the entire config. For example, let’s say it’s 2009 (oh 2009 <3) and you’re writing a rest crud app. You could write out every route for a given resource, or you could just include a rest module that merges in REST routes for a given resource and connects them to handler dispatch keys following a convention. That module is also configurable. More magic, less control, but it’s magic on demand like you said in the video for those places where it’s just fine. RAD I think it seemed very open to change, but every attr is wrapped in a macro defattr. Macro’s are less composable than data. It’s harder to generate macro’s without generating a code file or knowing about the macro’s internals. Do you think it’s possible to have RAD be expanded from a datastructure instead of macros? That way other libraries, people, could hook into that part as well, and even generate RAD schema’s based on other inputs etc..

So defattr just registers the attribute for you…it just defs a map otherwise, so the answer there is “yes, easily”

you could collect them all up into a schema map, and then call a funciton to build the system

this is 4 days of dev, so API is not set in stone on any angle

Of course not, that’s why I’m intervening so annoyingly

But that’s great!

If that’s the case, this could be huge imo

One goal is great error messages, so I sometimes lean on macros because they can give you immediate feedback when you screw up and good error messages

and clojure still sorely lacks that

ah i see

My defsc macro just calls configure-component!, but it checks things like “did you destructure something in props you didn’t query for”

saves tons of dev time

why would macros provide better errors?

gotcha

and I can give an accurate error: You didn’t query for X

and explain

much much better experience for beginners and me alike

Macros are compiler extensions…compile errors are useful in many cases where static analysis can tell you abt problems

core async isn’t even possible (as designed) without macros that convert clojure into state machines…they pre-compile your clojure into different clojure

I realised I could’ve summarized my shpiel by could rad be data driven instead of macro driven haha

exiting stuff @tony.kay! Have fun at the conj 🙂

conj just ended…headed out today. RAD is data-driven…but I agree with your point, perhaps macros are not right in the data model at all

simple enough the check the maps later

RAD is 4 days of conference-driven development…design work was not in any way careful 😜

but it shows how easy Fulcro + Pathom are starting to make things

I've started to enjoy mount that I discovered via fulcro template. It's way less complexity than component and yet a library. One can adopt (like I did) or go for other library or framework (like duct). It is a lovely choice because it reduces the complexity.

I just did a meet-up about where Fulcro is going, for contributors…here are the slides if anyone wants to help: http://book.fulcrologic.com/Fulcro-needs.pdf

just start to study fulcro via the video tutorial on youtube. this is really awesome.

I wonder is there something tell about how to do routing with fulcro?

I'm building out a simple poker game. My application has a Deck component. My understanding is that I'll only need a single :deck/id on which I will run mutations throughout the game. As cards are dealt out and collected back, :deck/cards gets updated to represent the change. Does that sound right? Is there any technical case where I should be create a new :deck/id and working with that instead of the original [:deck/id 1]?

@alex.sheluchin as what I learn from the video tutorial of fulcro, If you have some singleton component, you can give it a constant :ident, by provide a lambda:

:ident (fn [_ _] [:component/id ::name-of-this-component])

Does a singleton make sense? Is it the right abstraction? I guess I'm dealing with a conceptual conflict between data being immutable and maintaining the same id while creating a mutated copy.

@alex.sheluchin if you only have [:deck/id 1], you just ensure this ident is unique, IMO

it doesn't make much sense.

Hello, I have noticed that entity->pristine* stopped working from version 3.0.2 to 3.0.3 (it works like expected in all versions prior to 3.0.2). This can be tested using video example under tag rendering-part-2.

When pressing : on query tab on fulcro inspect chrome brings the settings. Are you experiencing this too ? Do you know a way to disable this shortcut ?