react

Roman Liutikov 2021-10-01T08:00:17.064500Z

not that hard actually (.-current react/__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED), but it may break in the future

lilactown 2021-10-01T16:01:23.064800Z

I wonder what react devtools will show for your props

Roman Liutikov 2021-10-01T16:04:03.065700Z

I think it’s not different from #js {:args [...]} props passing style, which shows implementation details of a data structure

lilactown 2021-10-01T16:39:05.065900Z

ah ofc

lilactown 2021-10-01T16:43:53.068400Z

how would this look from the other side? i.e. element creation

lilactown 2021-10-01T16:46:17.070600Z

components written like this can be just given the map, so you can do something like:

($ foo {:foo "bar" :baz [1 2 3]})
for JS components, you'd want to ensure you passed in JS objects instead
($ lib/Foo #js {:foo "bar" :baz #js [1 2 3]})

lilactown 2021-10-01T16:47:13.071200Z

I don't hate it. although you'd have to detect in $ to handle either JS objects or maps when associng in children

lilactown 2021-10-01T16:48:57.071700Z

perhaps js$ would better differentiate