Hey HN, I am Shardul - I am the other co-founder. Link to try the plugin: https://plugins.jetbrains.com/plugin/18529-unlogged
Connect with us: https://discord.gg/Hhwvay8uTa
Atomic Run & Direct Invoke Demo: https://www.youtube.com/watch?v=W0hAWx8EXcY
Happy to answer any questions you may have.
> without the need to execute the whole call hierarchy. (e.g. an HTTP endpoint)... > “Evaluate Expression” was quite useful in exploring new codebases and checking return values of my own functions as a sanity test.
Keep pulling on this thread... pretty soon you'll be writing unit tests!
Isn't this just reinventing the wheel and just replicating a built in IDE feature? I.e. what is wrong with Intellij's existing right click-execute on a single junit test method to debug and inspecting variables that way?
Also this is seems to be unit testing, E2E (or to be precise "component") testing in my experience is what takes much longer and is where time is lost constructing the fixtures, but importantly E2E tells you if you've made stupid mistakes like using GET instead of POST, or have an XML serialiser overriding the JSON one you intended, which you don't pick up in unit tests.
Now if you could somehow save an entire VM stack/state of a system for E2E tests that wasn't brittle to code change, that could just rebuild that state with a single line of code, that would be my dream time saver. The closest I've seen anything like that is recording HTTP request responses or serialising individual Java objects to JSON and using those as fixtures...
when i want to play with java stuff interactively i just actually open it up in clojure repl
The reloading part reminded me about https://www.jrebel.com/
[dead]
[dead]
An extremely complicated solution for a problem which does not actually exist.
That's really cool. I think there's still a lot of untapped potential in Java & Kotlin tooling, despite how far ahead of most other languages the IDE story is there anyway.
Your HTTP use case was a good one as that is still very tedious generally. There are some less well integrated solutions that have come up from time to time, but in general being able to run the HTTP request once and from then on mock the request/result easily would be great.
Hot reload seems to be something that comes and goes. Android Studio has had it and then not had it and then had it again several times. The cases in which it works seem to be fairly arbitrary. Improvements in this space would be great.