Fork me on GitHub
Slack Archive

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

2019-08-17

Channels

#clojurescript
<
2019-08-17
>
martinklepsch10:08:21

I’m looking for a datetime picker but there’s so many of them. So far this one seems popular and light http://projects.wojtekmaj.pl/react-datetime-picker/ — would be curious what others have used and how it worked out?

kleopatra15:08:14

We have been using this -> https://github.com/arfedulov/semantic-ui-calendar-react, has worked nicely so far:)

Lu11:08:57

I used the airbnb datepicker.. it works fine ✅

gdanov14:08:54

hi, I have trouble with :externs I'm using puppeteer (node.js lib to drive Chrome) and trying to use the hack mentioned here: https://swannodette.github.io/2014/03/14/externs-got-you-down but no luck

gdanov14:08:55

any hints what I could be doing wrong (or when the hack does not apply)? I tried also to make my own extern file as part of the project but I don't get any meaningful feedback and it seems to be not picked up so that's dead end for me

thheller14:08:06

what "hack" are you talking about?

thheller14:08:36

using the JS file itself?

gdanov16:08:22

I've enabled the extern inference as explained in the doc already. However I can't figure out what's the easiest way to add custom my_namespace_extern.js in the project so that I can specify more detailed hints. I really don't want to create full-blown extern artefact cljsjs style

thheller16:08:25

adding externs file is done via :externs ["path/to/externs.js"] in the compiler options. that hasn't changed.

gdanov16:08:29

thanks. I tried this but it didn't seem to have effect. The path can be to a js file in my source dir, right?

thheller16:08:40

I'm not sure how CLJS currently handles this by default

thheller16:08:03

it is either a file path or a resource path (ie. path on the classpath)

thheller16:08:33

just add both and see. also make sure you write the externs correctly since it is pretty easy to make mistakes there

gdanov17:08:27

well, I put all variants (absolute path, resource path) and I don't get any feedback even when the file doesn't compile. That's very frustrating, doesn't the compile dump anything?

thheller18:08:53

what do you mean when the file doesn't compile? externs only strictly affect renaming? compilation is not affected otherwise?

gdanov20:08:32

I mean the externs js file is syntactically broken. anyhow, I figured it out to some degree: running cljs compiler from the command line uses my extern file, but if I run the same config via figwheel.main it doesn't use my externs

dnolen14:08:36

@gdanov I need to start deprecating some of those blog posts

gdanov16:08:21

well, you've stated it's a hack so I didn't have big hopes.

Drew Verlee19:08:07

which blog post? i'm reading some of them now. 😆

gdanov16:08:21

well, you've stated it's a hack so I didn't have big hopes.

gdanov16:08:22

I've enabled the extern inference as explained in the doc already. However I can't figure out what's the easiest way to add custom my_namespace_extern.js in the project so that I can specify more detailed hints. I really don't want to create full-blown extern artefact cljsjs style

gdanov17:08:27

well, I put all variants (absolute path, resource path) and I don't get any feedback even when the file doesn't compile. That's very frustrating, doesn't the compile dump anything?