Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2018-11-13

Channels

#fulcro
<
2018-11-13
>
tony.kay03:11:39

Incubator 0.0.17 is now up. Adds support for sending events on load errors (@wilkerlucio).

🚀 12
💥 8
tony.kay03:11:26

NOTE: Incubator 0.0.15 and above require latest Fulcro

sooheon06:11:00

Quick question, do fulcro dom components support this type of nesting shorthand? (dom/div :.section>.component>.text "hi")

eoliphant14:11:18

Not that I know of, I know reagent has something like that

Ahmed Hassan08:11:23

Can I use fulcro with re-natal? for native development.

claudiu08:11:22

@UCMNZLJ93 Should work. Don't know if there any example apps, but you do have root-render & root-unmount for React Native in the reconciler options http://book.fulcrologic.com/#_useful_reconciler_options

Ahmed Hassan08:11:44

It works for Om.next, so I think should work for fulcro too.

tony.kay16:11:48

I know people have gotten it working without issue, bu I don't support it directly

❤️ 8
kirill.salykin09:11:36

is it possible to disable :ui/loading-data update for specific load? :marker false seems like doesnt

claudiu10:11:36

@kirill.salykin don't think so. that's a global marker that applies to all loads. You if want it to not apply for a certain load think using a mutation with df/load-action might do the trick, since the ui/loading-data is just for df/load.

tony.kay16:11:30

Remember that load markers can have names...it doesn't have to be "true", then you can use the marker table directly without any overwrite of UI data.

claudiu16:11:20

@tony.kay ahh yep. But there is no way for a load or load-action to bypass the ui/loading-data flag right ?

tony.kay16:11:57

right, but just don’t query for it 🙂

claudiu10:11:02

U're welcome. :)

kirill.salykin10:11:19

(df/load-action env :current-user UserSettings {:target [:tmp/current-user]})
If I do like this - then :current-user is set to nil if I load :current-user directly - login screen flickrs, because current-user was updated (even if all fields are the same) please advice is there anything I can do in this situation?

kirill.salykin10:11:42

I think I found, it replaces :current-user with :fetch-state

kirill.salykin10:11:47

is there a way to avoid it?

kirill.salykin10:11:01

seems like marker false fixes it but load-action still updates the :ui/loading-data field 😞

tony.kay16:11:02

Is supports the same options, including :marker

claudiu11:11:05

@kirill.salykin ah snap. Another approach worth looking at might be http://book.fulcrologic.com/#MutationJoins

kirill.salykin13:11:57

I found workaround, before showing loading gif check that all load-markers/by-id are “background”