I am trying to use shadow-cljs for a Jira Addon, but when I load shadow in watch mode, there is apparantly alread a goog.string defined and some other stuff which clashes and make the whole dev mode of shadow fail. Anyone here know a trick to prevent that?

I am getting all kind of errors like this 😞

@mitchelkuijpers hmm thats odd. is there already a goog version loaded on the page?

just check goog in the console without loading the .js generated by shadow-cljs?

@thheller Yes there is already something there

hmm yeah thats a problem. there can only be one development build loaded at a time

are there two different CLJS dev builds on the page?

@mitchelkuijpers you can probably "fix" the warning by adding :prepend "goog.isProvided_ = function(name) { return false; }; to your base module

but it may break a bunch of stuff in other places if you just overwrite the already loaded code

I'm trying to use https://github.com/gregthebusker/react-confirm-bootstrap#readme in one of my shadow-cljs projects. So far, I've been able to add other components, but I seem to fail this one: The example in js:

var Confirm = require('react-confirm-bootstrap');

    var ConfirmAction = React.createClass({
        onConfirm() {
            // Preform your action.
        },

        render() {
            return (
                <Confirm
                    onConfirm={this.onConfirm}
                    body="Are you sure you want to delete this?"
                    confirmText="Confirm Delete"
                    title="Deleting Stuff">
                    <button>Delete Stuff</button>
                </Confirm>
            )
        },
    });

(ns ....
  (:require ["react-confirm-bootstrap" :default Confirm]))

      [:> Confirm {:body      "question"
                 :title     "whatever"
                 :onConfirm #(println "confirmed")}
       [:span "push me"]]

Not sure if it's reagent or shadow-cljs related, actually 😛

@kurt-o-sys probably ["react-confirm-bootstrap" :as Confirm] not :default

when I use :as: Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object.

hmm ok

not sure about that library... may be something weird in there.

@thheller I think I am first going to check if I can turn the other one in release mode

@kurt-o-sys maybe it just doesn't support a span?

🙂

[:> Confirm {:onConfirm #(println "test")
                   :title "title"
                   :body "body"}
       [:button "test"]]

it looks like it is cloning the children and adding props

that won't work with reagent

oh, ok... so, no way to solve that one?

(r/as-element [:button "test"]) maybe

ok, will try 🙂

or you can just leave out the button altogether and specify :buttonText

oh, right. may work fine - although I wanted just an icon there, but well...

as-element should work

not sure how reagent typically deals with this though

https://github.com/gregthebusker/react-confirm-bootstrap/blob/master/src/Confirm.js#L72-L90

lol, you know what, it seems it does work, but I can't see the dialog that pops up... It's hidden behind the other stuff for some reason.

hmm actually this should probably work in reagent

ah yeah maybe just z-index 😛

trying, but nope. Not sure where it's gone.

ok... so it's the opacity that was set to 0, and fade didn't seem to work fine.

@mitchelkuijpers its not just goog. any other namespace will have the same issues (eg. cljs.core). but no there is no way to adjust that

@thheller I’m giving a bit of hammock time to my static site generator and was just wondering where I can follow your thoughts and updates on building a “Gatsby like” system and the plugin system you mentioned some time ago that you will be adding for stuff like Sass. Would like to ensure what I end up building is in the right direction.

@grounded_sage I can't give you any details since I don't have them myself yet

the plugin system is actually already implemented so there is nothing left to do there

but the gatsby like stuff will not be part of shadow-cljs itself

it would just be using it like any other tool

for this to work you basically need a full framework like gatsby etc

so I'd probably build on top of fulcro myself

I'm playing with fulcro shadow-cljs template (nodemo) and I'm working through the fulcro book. I've been able to adapt the template to follow along with the book, but I'm getting the following compiler error when trying to build the :cards build:

The required namespace "cljsjs.marked" is not available, it was required by "devcards/util/markdown.cljs".

I did an npm install marked but still get the same error.

Hmmm, I wonder if I have an old version of devcards running since I can't see any dependency on cljsjs.marked in the devcards project.clj on github.

Ok I see that devcards "0.2.6" does have this dependency and the shodow-cljs documentation says that the solution is to npm install marked but the error still occurs.

Hmmm, I can't seem to npm install marked --save in such a way that will get devcard build to compile.

I guess it needs a shim.

Ok, made a shim for marked, but now I'm getting this errror: The required namespace "create-react-class" is not available, it was required by "devcards/core.cljs". but I thought the required shim for react already existed in shadow.

I guess I'll make a shim for this too...

Hmmm, puzzling - I see create-react-class in shadow-cljsjs project.

oops probably forgot to install it.

Ok, that was it - sorry for the noise.