joyride

Akshay 2025-04-16T08:51:18.809179Z

Hi, I ran the .joyride/scripts/example/write_a_file.cljs example and it works. Then i tried to run https://github.com/BetterThanTomorrow/joyride/blob/master/examples/.joyride/src/problem_hover.cljs but i do not see the message in the hover over panel when hovering over say:

(comment
  foo
  (remove 1 2 3))
Here are the steps that i did, just in case I am missing something: 1. Copy the example code to .joyride/scripts/example/problem_hover.cljs 2. Joyride: Run Workspace script > example/problem_hover.cljs Output Panel show:
example/problem_hover.cljs evaluated.
=> nil

pez 2025-04-16T08:57:03.133519Z

Hello! Long time since I wrote this example…

pez 2025-04-16T08:58:25.112629Z

Where is your test code located?

Akshay 2025-04-16T08:59:15.577749Z

joyride_hover tree .joyride 
.joyride
├── deps.edn
└── scripts
    └── example
        ├── problem_hover.cljs
        └── write_a_file.cljs

pez 2025-04-16T08:59:33.470029Z

I guess what I really want to know: Is the problem listed in the Problems pane?

Akshay 2025-04-16T09:00:25.460229Z

Yes

Akshay 2025-04-16T09:03:24.279859Z

Just making sure, i am expecting the message to show up in here.

pez 2025-04-16T09:15:21.799039Z

Hmmm. Maybe you haven’t called problem-hover/register-provider! ?

1
Akshay 2025-04-16T09:16:26.810219Z

Yes. You are correct. It works now.

pez 2025-04-16T09:17:14.081789Z

Cool. FYI I am not sure I recommend that script all that much. I think VS Code has fixed the problem it tried to solve.

Akshay 2025-04-16T09:17:53.847569Z

Oh actually I am trying to use it to show flutter function signatures for clojuredart.

Akshay 2025-04-16T09:18:16.145539Z

At least that the idea. Lets see what i can make.

pez 2025-04-16T09:18:19.847439Z

Awesome.

pez 2025-04-16T09:19:04.983099Z

I think CoPilot can help with the VS Code API. Function signatures has their own provider.

pez 2025-04-16T09:20:44.750739Z

Also, I think clojure-lsp should already be providing signatures? Does it not work for ClojureDart?

pez 2025-04-16T09:21:38.197149Z

There is an extension VS Code API Explorer that I can recommend.

Akshay 2025-04-16T09:21:48.938959Z

Please

Akshay 2025-04-16T09:22:02.183469Z

okay that the name "VS Code API Explorer"

pez 2025-04-16T09:22:12.427059Z

Let me check.

pez 2025-04-16T09:22:46.867199Z

Yes.

👀 1
pez 2025-04-16T09:24:48.879799Z

In combo with the Joyride REPL it is pretty nice. A bit of a poor mans tooling, but anyway. When there is something you wish the the Joyride REPL should show you in auto-completion, you can take it to the VS Code API Explorer terminal.

Akshay 2025-04-16T09:26:46.824929Z

Ah okay, i see. looks like it will be really helpful. Thanks again.

🙏 1
pez 2025-04-16T09:27:56.934229Z

And just holler here if you get stuck on something.

🫡 1
Akshay 2025-04-16T09:41:26.288989Z

Or do i need to call it from .config/joyride/scripts/user_activate.cljs

pez 2025-04-16T09:57:03.629609Z

Good question. Joyride will look for the workspace activation script in the classpath under .joyride in your workspace. scripts folder is good place. I think there may be a joyride command for creating a default activation script.

👍 1
Akshay 2025-04-17T17:35:19.817479Z

@pez Thanks for your help. Here is the initial woking version. https://clojurians.slack.com/archives/C03A6GE8D32/p1744911124442529?thread_ts=1744620092.518429&cid=C03A6GE8D32

👀 1
🙏 1