cherry

rads 2025-03-18T01:20:56.041219Z

If I notice a standard function from cljs.core is missing from cherry (e.g. random-uuid), should I make an issue for it? I realize there are some that might be missing intentionally and some that might not

rads 2025-03-18T01:56:35.339059Z

It looks like I was wrong about (random-uuid) since I just tested it and it works. Looks like I got confused from earlier (or maybe this changed since I bumped the cherry version recently) That said I think the question still makes sense. I made an issue for cljs.pprint to document it since that namespace is missing

borkdude 2025-03-18T06:59:59.866469Z

Yea issues make sense

borkdude 2025-03-18T13:49:05.990709Z

@rads what do you need from pprint, I'm adding just the pprint function now

rads 2025-03-18T16:29:13.282229Z

That should be all I need, thanks! With the latest changes it's now possible to set up a useful tap> handler without any extra dependencies:

(require '[cljs.pprint :as pprint])
(add-tap pprint/pprint)
(tap> :foo)

🎉 1