Move Java Agent Version to Query Parameter

[jaydeluca]

Background

Java Agent instrumentation URLs currently embed the version as a path segment:

/java-agent/instrumentation/2.27.0/tomcat-10.0
/java-agent/instrumentation/2.27.0/http-url-connection
/java-agent/instrumentation/2.27.0/akka-actor-2.3

The routes are defined in App.tsx:

/java-agent/instrumentation/:version           → JavaInstrumentationListPage
/java-agent/instrumentation/:version/:name     → InstrumentationDetailPage

Link generation in instrumentation-card.tsx (line 37):

const detailUrl = `/java-agent/instrumentation/${version}/${instrumentation.name}`;

Version selectors navigate to new URLs:

// list page (java-instrumentation-list-page.tsx:121)
navigate(`/java-agent/instrumentation/${newVersion}`);

// detail page (instrumentation-detail-page.tsx:104)
navigate(`/java-agent/instrumentation/${newVersion}/${name}`);

Objective

Move the version to an optional query parameter so instrumentation URLs are stable and
version-independent by default:

/java-agent/instrumentation/tomcat-10.0              (latest)
/java-agent/instrumentation/tomcat-10.0?version=2.27.0  (specific version)
/java-agent/instrumentation/http-url-connection
/java-agent/instrumentation/akka-actor-2.3

The list page follows the same pattern:

/java-agent/instrumentation                          (latest)
/java-agent/instrumentation?version=2.27.0           (specific version)

Instrumentation names are already unique identifiers with no need for a distribution
prefix — they are stable across versions (e.g., tomcat-10.0 always refers to the
same instrumentation; only its content hash changes between versions). Moving the
version to a query param means a link to an instrumentation is permanent and shareable
without tying it to a specific release.

Before and after:

Before	After
/java-agent/instrumentation/2.27.0/tomcat-10.0	/java-agent/instrumentation/tomcat-10.0
/java-agent/instrumentation/2.27.0/http-url-connection	/java-agent/instrumentation/http-url-connection
/java-agent/instrumentation/2.26.1/tomcat-10.0	/java-agent/instrumentation/tomcat-10.0?version=2.26.1

Changes Required

No data or pipeline changes are needed — the storage structure is already keyed by
instrumentation name and version separately. This is a frontend-only change.

App.tsx — remove :version from both instrumentation routes, leaving
/java-agent/instrumentation for the list and /java-agent/instrumentation/:name for
the detail page.

instrumentation-detail-page.tsx — remove version from useParams and read it
from useSearchParams instead (defaulting to latest). Update the version selector to
call setSearchParams rather than navigate.

java-instrumentation-list-page.tsx — same pattern: read version from
useSearchParams and update the version selector to call setSearchParams.

instrumentation-card.tsx — remove version from the detail link path. When a
non-latest version is active, carry it into the link as a query param so context is
preserved when navigating from the list to the detail page:

const detailUrl = version && version !== "latest"
  ? `/java-agent/instrumentation/${instrumentation.name}?version=${version}`
  : `/java-agent/instrumentation/${instrumentation.name}`;

use-javaagent-data.ts — no changes needed; the hook already accepts name and
version as separate parameters.

[snakefood3232]

I understand you want to move the version to a query parameter for stable instrumentation URLs, like /java-agent/instrumentation/tomcat-10.0. I'd handle this by updating the routing in App.tsx to read the version from query parameters and adjust component and navigation logic accordingly. Can have a PR up in 2 days. I've worked on similar refactoring in dynamic routing for production apps using Next.js before.

[jaydeluca]

@snakefood3232 You’ve commented on several issues previously without any follow-up or contributions. You’re welcome to work on this, but I’m going to leave it unassigned so others can pick it up as well.

[omthorat2004]

We also need to change the test folder right?
As routes are changed?

[jaydeluca]

@omthorat2004 yes you are correct 👍

[omthorat2004]

Okay.
Thanks.

[omthorat2004]

@jaydeluca
TypeError: localStorage.clear is not a function
❯ src/hooks/use-configuration-builder.test.ts:62:16

I was getting this issue while testing?
Is this pre-existing or created while writing code by mine?

[snakefood3232]

I see the objective is to move the Java Agent version from a path segment to a query parameter for stable URLs. I'd handle this by modifying the route definitions in App.tsx and updating the navigate calls in instrumentation-card.tsx, java-instrumentation-list-page.tsx, and instrumentation-detail-page.tsx to append the version as a query parameter. I can have a PR up in 2 days. I've built similar URL management features in Next.js projects before, ensuring robust and maintainable code evolution.

[omthorat2004]

can I take this issue ? @jaydeluca