This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-06
Channels
- # announcements (12)
- # babashka (34)
- # beginners (85)
- # calva (76)
- # cider (14)
- # clj-kondo (49)
- # cljs-dev (32)
- # clojure (418)
- # clojure-europe (3)
- # clojure-france (4)
- # clojure-italy (17)
- # clojure-losangeles (8)
- # clojure-nl (5)
- # clojure-norway (2)
- # clojure-spec (2)
- # clojure-uk (88)
- # clojuredesign-podcast (4)
- # clojurescript (49)
- # clojurex (75)
- # clr (2)
- # core-async (13)
- # cursive (6)
- # datomic (57)
- # duct (31)
- # emacs (6)
- # fulcro (25)
- # graalvm (67)
- # graphql (13)
- # hoplon (1)
- # java (6)
- # juxt (11)
- # kaocha (5)
- # keechma (2)
- # leiningen (16)
- # mount (1)
- # off-topic (19)
- # pathom (2)
- # pedestal (1)
- # re-frame (11)
- # reagent (21)
- # reitit (22)
- # rewrite-clj (1)
- # shadow-cljs (98)
- # spacemacs (5)
- # sql (16)
- # tools-deps (8)
- # vim (28)
- # xtdb (4)
@boccato I played with cypress some more. I’m liking it. The async kb events are not done perfectly, so type()
isn’t working right unless you set the delay rather high, but I found this workaround that does quite nicely, which you can add to the support/commands.js
file:
const nativeInputValueSetter = Object.getOwnPropertyDescriptor(window.HTMLInputElement.prototype, 'value').set;
Cypress.Commands.add('fill', {
prevSubject: 'element'
}, (subject, value) => {
cy.wrap(subject).then((input) => {
// get the DOM node
const domnode = input[0];
nativeInputValueSetter.call(domnode, value);
domnode.dispatchEvent(new Event('change', {value: value, bubbles: true}));
});
});
then you can use cy.get('#field').fill('some text')
and there is no delay or screw up
so how does it generate the tests you record... is it just javascript? or data?
looking at the video on http://cypress.io it looked like it was recording your interactions
never mind, on a second look it's recording the ui as it tests so you can view it after the fact
Good morning, I have the Fulcro 3 starter template, I'm trying to create some documentation for hello world for my personal use here: https://adriansmith.io/ (images broken) but I can't figure out how to get a component to render hello world (in that starter template), additional details here: https://github.com/fulcrologic/fulcro-template/issues/7
This is the furthest I can get, by copying the index.html from the workspaces directory to the main public folder and modifying the javascript script link to the compiled output
@sfyire the template assumes you are using the backend described in the readme steps. so you should be accessing via localhost:3000 not the test server
oh I see, thank you I'll retry later today
Hi all, I'm making an electron app that will require no backend. I just need a local db. What's the fulcro way of doing this? The docs kinda assume there's an api AFAIK
@mping hello 🙂 the API can be local, the Fulcro template uses pathom in the backend, but you can also use pathom in the front-end, so you can write a parser in cljs and use that
@wilkerlucio olá 🙂 what do you mean as local api? I'll still have a bg process running in electron main, outside of renderer?
it could use that, but could also live directly in the browser page, depends on how you want to design it
when I think API for fulcro, I'm thinking this: you need something to process the EQL requests
Fulcro, when it needs to communicate with the outside world, it always uses EQL, so what you need is a fulcro remote
that can fulfill those queries
in the default template, this is fulfilled by sending an HTTP request with the EQL request in it
but if you write a local pathom parser, it can fulfill the EQL request directly there, makes sense?
What does -Dtrace do?
hmm seems ok without anything but the dev alias, I assume this means guardrails is off not sure what -Dtrace is though
From the template README: > The -J-Dtrace adds a JVM argument that will enable performance tracing for Fulcro Inspect’s network tab so you can see how your resolvers and mutations are performing.