yes, everything, unless you explicitly filter some files out using :uberjar-exclusions

I see!

Thank you!

On that same note, are there any guides you recommend to compile a leinigen backend and shadow-cljs frontend? And dockerise the solution?

is your backend serving the assets compiled by shadow-cljs?

asking because there is no silver bullet ) every situation is unique and requires some special care

Not to my knowledge. Currently am using a separate project.clj for the backend and separate shadow-cljs.edn for the frontend

then I would recommend to read at this link - https://shadow-cljs.github.io/docs/UsersGuide.html#release understand what artifacts will be generated for production usage then general advise - split your docker image preparation into stages: • generate your client assets • build uberjar with those assets included • add uberjar to some thin image with jdk. An entrypoint could be something like java -jar /path/to/uber.jar

Would this only be for the frontend? Or is this if I use shadow-cljs for both frontend and backend? o: (Am only aware I can use project.clj for both)

idk, nether used shadow-cljs for backend

a jar file is basically a zip file, you can inspect it and see yourself. on my BSD system, tar works. tar xvf foo.jar | grep *.py

> Meaning any .csv and even .py I might be calling with shell/sh these will end up in the jar if they are on the calculated classpath (eg. inside the resources/ directory with a default setup), but for shell/sh to provide the document to an OS process it needs to be copied out of the jar into a location the process can use (eg. by spitting it to a file, or providing its contents to stdin etc.)

Thanks! I’ll probably need to change some of the problems to adapt for how the tests now work.

Problem 4 is definitely a bit weird. I don't know how many others assume multiple input forms...

I think problem 6 has the same problem

@pez @seancorfield

It's probably in the low numbers we find this. Please file issues about it.

oke

@pez 4 issues I made already and I stop now because Im going on holidays for 2/ 3 weeks

As you deserve! Have a blast!

we hope, as we look at the weather expectations we get 2 weeks rain. and that is not fun with camping with a tent

@pez thanks for solving the first issues. I will test them after im back from the holidays

I think for the other issues it is more about that the user needs to read the README a bit careful. I have pushed an update to the readme where it is a bit more clearly stressed that all problems cannot be solved by redefining __,

::+1:

not all there is one possible namespace problem in it I think

issue 3

You did npm install ... and it works on the REPL but not in a file?

Correct. It works in shadows repl but not the file.

For the file, I get a JS object when importing but I can’t run the same functions on it- ie I get a “not a function” error

This — (:require ["…" :as …]) will work only within the (ns …) block. Notice that :require is not a function that can import dependencies on its own, but a keyword - the ns form understands it. In standalone mode, you need to use require (notice - not a keyword). Again, I don’t do CLJS much so there may be quirks, but that is the idea.

When I say standalone, I meant top-level form that stands on its own.

Right yeah so in the repl I did the function (require ‘[“…” :as x] ) and then in the file i did (:require [“…” :as x]). They should import the same thing but they did not

Not sure I understand the “did not import the same thing” part. Did one of them work?

Yes the repl one worked and I can call the appropriate api functions, but the file one did not. While it imported a JS object, I cannot call the same functions on it.

The file version - where are you calling (:require…)? Inside the top-level (ns… (:require ["…" :as …]) or by itself?

Yeah it’s inside the namespace declaration

Got it. Is there any more context you can provide? More code in the context of evaluation, or relevant parts of the error you see in the logs?

Yeah sure. So in the shadow node-repl, I write (require '["@babajidemm/african-countries-api" :as x])

Then I write (.. x (byName "Algeria") -body toString) and get the proper body response

In the file namespace, I write: (ns african-countries.data (:require ["@babajidemm/african-countries-api" :as africanCountriesAPI])) (defn getCountryByName [] (let [info (.. africanCountriesAPI (byName "Algeria") -body toString)] (js/console.log info)))

I call this function, get this error twice: Uncaught TypeError: module$node_modules$$babajidemm$african_countries_api$index.byName is not a function at Object.african_countries$data$getCountryByName [as getCountryByName] (data.cljs:9) at eval (views.cljs:24)

Lastly, this is important: It works in the node-repl but not in the browser-repl. In the browser-repl I get an error that says: "Execution error:  "Module not provided: ./v1/lib/CountriesService"

Ok - I tried something and I don’t think I have a good answer for you. But the library you mention did not work for me in the “browser” REPL, and worked fine in “node”. Node was fine both repl and file

Ah - posted at the same time. It could be that the module format of the @babajidemm/african-countries-api isn’t supported in browsers and needs some special handling for browsers. You may find better support in the #clojurescript channel I think - a more focused group for cljs.

Thank you @U06KGH6LB, I think you're right. I think the difference is the module is build for a backend node process

the namespace :import clause is just a syntax for what import does at the top level, both work in a file or a repl (though for obvious reasons you are more likely to have a carefully crafted ns clause in a file)

in fact the list of things that are different between file and repl in clojure are extremely small (unless you count conventions / coding style differences, that's a much bigger list)

oops yeah. didn't even notice that comment block. gonna have to pull it out...

If it weren't in a comment expression would using a source file from a non-library be possible?

@cdimara If you're using deps.edn and the Clojure CLI (rather than lein) then you could have a git dependency on the http://clojuredocs.org source code and then you could reference its namespaces in your code.

However, https://github.com/zk/clojuredocs is a Leiningen project so you'd have to override that in deps.edn (`:deps/manifest :deps`) and then you would also need to explicitly specify in your deps.edn file, the dependencies from clojuredocs' project.clj file.

So it's possible but non-trivial for some older projects...

what would be the artifactID/version number if there's no .pom?

You use a git dependency instead.

(! 658)-> cat deps.edn 
{:deps {io.github.zk/clojuredocs {:git/url "" :sha "28f5ee500f4349039ee81c70d7ac40acbb19e5d8" :deps/manifest :deps}}}

Although in this case the checked out repo doesn't have the right structure to be able to require clojuredocs.env -- b/c it doesn't match the default (and we had to override the manifest type).

A big plus of the CLI and deps.edn is to be able to use repos from GitHub and GitLab directly without them needing to be deployed to Clojars or Maven.

For example: https://github.com/clojure/tools.build -- it has "releases" but they are only tags on GitHub -- it doesn't exist on Maven or Clojars -- but you can see in the README how to depend on a specific tagged release from GitHub directly.

You said "the checked out repo doesn't have the right structure to be able to require clojuredocs.env " Whats wrong with the structure?

If you make the :path ["src/clj"] the folders match the namespace.

Yes, but you shouldn't edit the checked out repo -- you should pretend it is immutable -- otherwise it won't work on someone else's machine.

got it

Thank you Sensei Corfield!

So, say you had a bunch of input say a vector of unknown numbers.

And your predicate was even?

if you do the group-by you get your results and they're labled by the result of your predicate.

you can do destructuring and hold on to your results forever.

yes. Thats if you don't need the other values.

But if you need them both AND you want to inspect a few, group-by allows you to do that work just once.

yeah

cool