i've been resistant to the idea of adding a .lazytest.edn or similar file, it increases maintenance burden, adds one more place to track state, etc. however, as i'm working on a --hook system, it does seem like it would be helpful to say in a single place "i always want to randomize suites in a namespace" or "i always want to profile my runs". what do y'all think?
Totally +1 for hidden files and respecting the $XDG_CONFIG_HOME var.
I think .lazytest/config.edn would be better, in a project and a user-level ~/.config/lazytest/config.edn too perhaps?
oh yeah? you prefer a hidden folder?
That's more consistent with LSP, Calva, Kondo, VS Code, etc.
And others...
And user-level stuff in ~/.config:
(!2009)-> ls .config
'Android Open Source Project' cef_user_data dconf google-chrome joyride nvm rest-client
Google clojure eas-cli-nodejs gtk-3.0 matplotlib polylith
JetBrains clojure-lsp exercism htop mimeapps.list procps
calva configstore glib-2.0 jgit nrepl pulse
(2025-12-17.21:12:22)-(~)alongside that, i have implemented a profiling hook that works exactly the same as the profile reporter, except it's a hook and thus isn't using hardcoded durations calculated by the runner. i am interested in removing profile or making it a no-op so i can remove the hardcoded duration calls (which will make the runner simpler overall). i wrote up a little bit of logic to include the profiling hook if profile reporter is included, which solves the problem of bridging the old way with the new. What do y'all think? Does anyone use --output profile at all? Or regularly?
Wot profile? 🙂
looks like i never documented profile hah, so maybe i can just rip this out and no one will notice