This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-15
Channels
- # arachne (6)
- # aws-lambda (3)
- # beginners (14)
- # boot (56)
- # cider (8)
- # cljs-dev (5)
- # cljsrn (11)
- # clojure (240)
- # clojure-dusseldorf (3)
- # clojure-greece (165)
- # clojure-italy (5)
- # clojure-romania (1)
- # clojure-russia (24)
- # clojure-uk (30)
- # clojure-ukraine (3)
- # clojurescript (29)
- # core-async (6)
- # css (1)
- # cursive (25)
- # datascript (6)
- # datomic (61)
- # dirac (1)
- # events (3)
- # hoplon (1)
- # instaparse (3)
- # jobs (4)
- # juxt (28)
- # lein-figwheel (7)
- # leiningen (19)
- # luminus (1)
- # lumo (2)
- # nyc (1)
- # off-topic (19)
- # om (25)
- # onyx (4)
- # parinfer (2)
- # pedestal (23)
- # perun (20)
- # re-frame (44)
- # reagent (20)
- # remote-jobs (3)
- # ring (3)
- # ring-swagger (5)
- # rum (12)
- # slack-help (3)
- # spacemacs (25)
- # specter (62)
- # sql (16)
- # unrepl (313)
- # yada (4)
@podviaznikov are you working on the new feature requests you submitted last night? If you are not, your timing is perfect :)
I have a pair-programming job interview tomorrow. I am supposed to pick a project to work on for the interview, and obviously Perun is at the top of my list. Implementing those two features would do nicely!
I only have boring ideas: docstrings + validation of return values of user supplied functions
@bhagany no, not working. That is the reason I submitted them in case someone would like to do them before me. So you are welcome to tackle those tasks
Perfect indeed:)
let me know if you need more details. I wasn’t very verbose in the description
I think I understand, but I'll be doing some prep this afternoon. If I have questions, you'll be sure to know 🙂
@podviaznikov okay, here's a question for you - is your purpose for the manifest.json file solely for "installing" the site on a phone? or do you want to support other web extension features?
I was thinking about just “installing”
basically straight from the HTML spec
@podviaznikov have you thought about how to handle cache invalidations, re: #180?
The idea I had personally was to pass build date as cache version. So every time site is build new cache version would be generated. But it’s definitely can be smarter. I would also look how other people do it (like gatsbyjs). So it’s open investigation task
if you have some other ideas, definitely share them