This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-18
Channels
- # announcements (19)
- # babashka (30)
- # beginners (51)
- # biff (12)
- # calva (20)
- # cider (27)
- # clara (20)
- # clj-kondo (19)
- # clojure (128)
- # clojure-canada (1)
- # clojure-dev (5)
- # clojure-europe (29)
- # clojure-nl (1)
- # clojure-norway (48)
- # clojure-uk (5)
- # clojurescript (6)
- # clr (37)
- # core-async (17)
- # cursive (2)
- # data-oriented-programming (2)
- # datahike (1)
- # datomic (5)
- # emacs (22)
- # exercism (1)
- # funcool (17)
- # humbleui (15)
- # jobs (1)
- # malli (44)
- # off-topic (11)
- # podcasts-discuss (1)
- # pomegranate (1)
- # react (1)
- # remote-jobs (1)
- # shadow-cljs (25)
- # tools-build (12)
- # tools-deps (70)
- # xtdb (24)
if you like awesome free grids could you please thumb up https://github.com/KevinVandy/material-react-table/discussions/328
➕ 2
You could cut the ticket to match-sorter-utils as well, seems they could fix it by wrapping their keys in double quotes
I could. But they are not going to do. I've asked on tanstack discord.
How can I monkeypatch a function in a JS object so that I can still call the 'original' function? I figured (let [f (.-f obj)] (set! (.-f obj) (fn [x] (prn "got" x) (f x))))
would work, but I'm getting Cannot read properties of null
errors when calling (f x)
.