v0.5.3

Changes

• Correctly analyse frame location in child modules in 6d84ce3

Full Changelog: v0.5.2...v0.5.3

v0.5.2

Fixes

• Fix assertion.context check operating on nil value in 8103d7a
• Fix frame-at-cursor resolution logic during gd in 88f77b3
• Fix more window tracking stale state issues in c3fb1d4

Full Changelog: v0.5.1...v0.5.2

v0.5.1

Fixes

• Fix clojure jar build using incorrect paths in 0eb3da3

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Changes

• Display test descriptions in overview in 5f16cb8
• Handle tests that are defined with metadata in 3a14798

  Closes #2

• Fix logic to switch back to previous window in e3b9a5d

  There is some logic which attempts to focus the last opened window when
  the float layout is closed or unmounted.

  This worked by tracking the currently active window prior to mounting
  the float UI.

  The float UI is only constructed once during the life of the neovim
  instance, which means if the original window is dropped at any point
  then the switching logic would fail with a nasty exception.

  This commit fixes the problem by always re-setting the last active
  window on every remount, instead of only once when the UI struct is
  first initialized.

  There is an additional fix wherein if we unfocused the float window due
  to openening another float window, then both would be closed.

  This is resolved by first checking if the clojure-test UI is actively
  focused before attempting to run the window switching logic.

• Always reference correct exception when running gd in 4444dc5

  When running gd from an analyzed exception (not an exception from a
  test) the gd logic would use the first exception instead of the last.

• Expand exception gd to support multiple locs in c25b933

  This is a bigish change which adds support for picking the desired frame
  to navigate to from an exception when using the gd functionality.

  This required moving the location analysis to the JVM backend and
  therefore requires updating the companion lib to the latest release if
  you want exception gd to continue working.

  Now when using the analyze_exception backend API or when collecting
  test reports with exceptions (which come pre-analyzed) the exception
  stack frames come pre-populated with a :location key. This, if
  present, points to the file and line information on disk which correlate
  to that frame.

  This means two things:

  1. We don't need to do an expensive, looping lookup per frame when
     navigating any more. This is a big performance improvement.
  2. We have all the location information up-front which means we can
     render this information in the exception UI!

  So, this means the exception UI now indicates to the user which stack
  frames point to locations on disk (and therefore are gdable). It also
  means we can much easier turn this into a select prompt to the user to
  allow them to pick the frame they want to navigate to.

  Lastly, the exception buffer has been updated so that you can gd on a
  specific frame to skip the frame picker and navigate directly to that
  frame.

New Contributors

• @yannvanhalewyn made their first contribution in #1

Full Changelog: v0.4.0...v0.5.0

v0.4.0

Changelog

• Improve exception go-to-definition in eaf7773
• Add APIs to run failed tests and open last reports in 7435108
• Stop running tests when UI unmounts in e988843
• Sort tree nodes in order of failed/passed/pending in ad2d111
• Explicitly filter for failed reports in 7d22daa
• Destroy active_ui on unmount in f3bb0b7
• Handle exceptions from async tasks in 744e0f3
• Refactor UI components and layout APIs in 8ba9988
• Render summary when hovering on parent node in 430d222
• Handle exceptions with no messages better in 6aeddcd

Full Changelog: v0.3.0...v0.3.1

v0.3.0

Full Changelog: v0.2.0...v0.3.0