Fork me on GitHub

if anyone is looking for an easy contribution: fixing docstring formatting issues like this one would be great:


that was supposed to be a bullet list…but I forgot to put a * or - in front of each one, for example


wikilinks to nses would also be nice…like See [[com.fulcrologic.thing]]


have been trying react-native-template out, with fulcro (3.1.5) / fulcro-native (0.0.5) / fulcro-inspect-electron (2.3.0-RC2) and apparently hitting this issue which is raised by c.f.f.i.websocket-preload when running in iOS simulator it’s not critical as sente downgrades to :ajax type on it’s own and you can just dismiss the error, but seems weird. i looked into more verbose logs, but wasn’t able to identify the problem


vanilla fulcro-native-template is running just fine


well, no, couldn’t make inspect-electron (2.2.1) connect to iOS simulator for vanilla fulcro-native-template: no errors, even tried to start inspect ws manually, still “no app connected”


for the latest fulcro / fulcro-native / fulcro-inspect-electron inspect is working fine (but with sente downgrading to :ajax as mentioned above)

Robin Jakobsson15:01:22

Has anyone successfully done Meteor style subscriptions for Fulcro -> Datomic -> Fulcro? It says in the book that “You could use a “custom” websocket remote to adapt to any existing GraphQL infrastructure that supplies such automatic updates.“. Would be really interesting to see an example of such infrastructure.


@fjolne.yngling thanks for the feedback. downgrading to ajax won’t hurt anything for inspect, but sad that sente isn’t working well there.


@jakobssonrobin I’ve worked on more than one project where that kind of thing was desired. Fulcro’s side of it is usually trivial or very easy….it’s always scaling the infrastructure to figure out what changed on the server that is the hard problem. That’s both why metoer is such a unicorn, and also why it isn’t a very appealing unicorn (getting it to work with anything but a kind of crappy db is very hard).


you are not going to find a general library that fixes that problem, because it isn’t a generic problem…it is very much tied to the database infrustructure, deployment, etc. You may find a database or caching solution that tries to address it, but looking for a pre-build full-stack meteor that works with any database you want to use just isn’t a thing AFAIK

Robin Jakobsson10:01:06

Thank you very much for the thorough answer :thumbsup: .


@tony.kay also maybe it worth mentioning in the README that CSRF protection is disabled in the template so that you need to take care of it by yourself. AFAIU the easiest approach would be to have separate cookies and API endpoints (with and w/o CSRF check) for web and mobile


i’d be happy to make a PR though :)


just to clarify, i wouldn’t expect a general template to handle all the security concerns, it’s just that CSRF protection is enabled by default in main fulcro template, so people coming from there (like me) can accidentally miss it


@fjolne.yngling sure, I’d take a PR on that