Yes, it's a command in portal but you can't execute them outside of the UI... yet

What runtime api would you expect?

(portal.api/eval instance '(portal.command/history-first))

It would be really nice if (some of) the various portal.command functions were exposed via a JVM (backend) API -- not all of them make sense perhaps. What would instance be there?

The result of calling open

Ah, makes sense. And it would allow you to eval any configured command/function?

Portal already has bidirectional communication so this would be pretty easy, just a matter of api design

Not sure eval is the right name. Perhaps (portal.api/command instance (portal.command/history-first)) as a macro wrapper so you don't forget to quote it?

Yes, I have sci in the client runtime already so I would expose / enable all the commands and some other things to allow some scriptability

And you're already considering a nicer API to install new functions?

Kinda, I was thinking you could pass p/open a function like :commands which gets invoked anytime a user wants to run a command with the currently selected value and can return command that would make sense for that value

Ah, makes sense. What I've done right now kind of bypasses those checks and makes them "always available".

Also... can we get that list of commands in alphabetical order instead of hash-map-random-key order? 🙂

My OCD is being traumatized by the non-alpha ordering right now 😆

Yeah, that should be really easy 👌

And done https://github.com/djblue/portal/commit/2d971f2bdcd974352d2b0f74212babbf13eba6fe

I wish there was an easier way to run dev versions of portal from git :thinking_face:

Also I think the reason I lean eval is that it enables user provided commands to start doing more. Like get more values from the user before it returns 👌

Ooh, nice! OK.

I was just looking over the dev/build/test process -- I don't think I could even run that locally. I'm on macOS 10.12 (for reasons) and I know planck won't build/install on that -- and it won't currently build/install on WSL2 (Ubuntu) last I tried either. Plus I don't think I have node/npm/npx on either machine (I may have it on the Mac) and I don't have bb installed anywhere 😐

I wonder if I can save the main.js that is built during CI :thinking_face:

Maybe have everything successful CI run deploy a snapshot to Clojars?

(I don't know how the Clojars folks would feel about every project publishing every snapshot tho'... I'll go ask them!)

Toby Crawley from the Clojars team says that would be fine. Several projects already do it and it isn't an issue -- so there's a possible way for folks to test Portal builds as they happen.

I just updated next.jdbc's GH Actions to build a snapshot for every push to the main branch and deploy it to Clojars automatically.