src/components/ComponentVersion/index.ts (1)

1-4: Use configured path aliases for imports in this new module.

Please switch these new relative imports to the repository aliases to match import restrictions and keep layering consistent.

♻️ Proposed refactor

-import { k8sQueryGetResource } from '../../k8s';
-import { ComponentModel } from '../../models';
-import { RouterParams } from '../../routes/utils';
-import { createLoaderWithAccessCheck } from '../../utils/rbac';
+import { k8sQueryGetResource } from '~/k8s';
+import { ComponentModel } from '~/models';
+import { RouterParams } from '~/routes/utils';
+import { createLoaderWithAccessCheck } from '~/utils/rbac';

As per coding guidelines: "Use absolute imports with configured path aliases: ~/components, ~/types, ~/k8s, ~/utils, ~/models, @routes."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/components/ComponentVersion/index.ts` around lines 1 - 4, Update the four
relative imports at the top of this module to use the project's configured path
aliases: replace '../../k8s' with '~/k8s' for k8sQueryGetResource,
'../../models' with '~/models' for ComponentModel, '../../routes/utils' with
'@routes/utils' (or '@routes' variant) for RouterParams, and '../../utils/rbac'
with '~/utils/rbac' for createLoaderWithAccessCheck so the module uses the
absolute alias imports required by the coding guidelines.

src/components/ComponentVersion/ComponentVersionDetailsView.tsx (1)

20-20: Use absolute import path for DetailsPage.

The import should use the configured path alias for consistency with the rest of the imports in this file.

♻️ Proposed fix

-import { DetailsPage } from '../DetailsPage';
+import { DetailsPage } from '~/components/DetailsPage';

As per coding guidelines: "Use absolute imports with configured path aliases."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/components/ComponentVersion/ComponentVersionDetailsView.tsx` at line 20,
The import for DetailsPage in ComponentVersionDetailsView uses a relative path;
update the import to use the project's configured absolute path/alias (e.g.,
import DetailsPage from the alias that resolves to the DetailsPage module) so
that the DetailsPage import follows the codebase's absolute import convention
and matches other imports in this file.

src/components/ComponentVersion/tabs/ComponentVersionDetailsTab.tsx (2)

49-81: Remove unnecessary fragment wrapper.

The fragment wrapper (<>...</>) is unnecessary since there's only a single child element (DetailsSection).

♻️ Proposed fix

-  return (
-    <>
-      <DetailsSection title="Version details">
+  return (
+    <DetailsSection title="Version details">
         <DescriptionList>
           ...
         </DescriptionList>
-      </DetailsSection>
-    </>
+    </DetailsSection>
   );

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/components/ComponentVersion/tabs/ComponentVersionDetailsTab.tsx` around
lines 49 - 81, The JSX return in ComponentVersionDetailsTab wraps the lone
<DetailsSection> in an unnecessary fragment; remove the fragment wrapper and
return the <DetailsSection> element directly so the component returns a single
root element. Update the return expression that currently wraps
<DetailsSection>...</> to just <DetailsSection>...</DetailsSection>, leaving
inner children (DescriptionList, DescriptionListGroup, LatestBuildSection, etc.)
untouched.

---

18-18: Use absolute import path for DetailsSection.

The import should use the configured path alias for consistency.

♻️ Proposed fix

-import { DetailsSection } from '../../DetailsPage';
+import { DetailsSection } from '~/components/DetailsPage';

As per coding guidelines: "Use absolute imports with configured path aliases."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/components/ComponentVersion/tabs/ComponentVersionDetailsTab.tsx` at line
18, Replace the relative import of DetailsSection with the project's configured
path alias: update the import statement that currently imports DetailsSection
from '../../DetailsPage' in ComponentVersionDetailsTab.tsx to use the absolute
alias used across the repo (e.g., the configured alias for the DetailsPage
module) so DetailsSection is imported via the project's path-alias instead of a
relative path.

src/components/ComponentVersion/__tests__/ComponentVersionDetailsView.spec.tsx (1)

72-83: Consider moving namespace mock inside beforeEach for better test isolation.

The mockUseNamespaceHook('test-ns') call at line 73 is outside beforeEach, which may work but could lead to unexpected behavior if tests modify namespace state. Moving it inside beforeEach ensures consistent setup for each test.

♻️ Suggested improvement

 describe('ComponentVersionDetailsView', () => {
-  mockUseNamespaceHook('test-ns');
-
   beforeEach(() => {
+    mockUseNamespaceHook('test-ns');
     useParamsMock.mockReturnValue({

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@src/components/ComponentVersion/__tests__/ComponentVersionDetailsView.spec.tsx`
around lines 72 - 83, Move the call to mockUseNamespaceHook('test-ns') into the
beforeEach block to ensure namespace state is reset for every test; update the
beforeEach that currently sets useParamsMock, useComponentMock,
mockUseIsOnFeatureFlag, and mockUseFeatureFlags so it also calls
mockUseNamespaceHook('test-ns') at the top (or call a reset/cleanup helper prior
to setting the other mocks) to guarantee consistent isolation between tests.

src/components/LatestBuild/__tests__/LatestBuildSection.spec.tsx (1)

9-15: Use the typed mock helper instead of as jest.Mock here.

These casts erase the hook/utility signatures, so the suite can return the wrong tuple or argument shape without TypeScript catching it. createJestMockFunction keeps the mocks aligned with the real APIs.

Based on learnings: use createJestMockFunction from ~/unit-test-utils/common for type-safe mock functions with specific signatures.

Also applies to: 25-26

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/components/LatestBuild/__tests__/LatestBuildSection.spec.tsx` around
lines 9 - 15, Replace the untyped jest.fn mocks for the hook and utility with
the typed helper: import and use createJestMockFunction from
'~/unit-test-utils/common' to create mocks for
useLatestBuildPipelineRunForComponentV2 and getCommitsFromPLRs so their
signatures are preserved (replace the jest.mock implementations that return
jest.fn() and any spots currently cast with "as jest.Mock" with
createJestMockFunction<T>() calls using the real function/type signatures);
ensure both the mock definitions shown for
useLatestBuildPipelineRunForComponentV2 and getCommitsFromPLRs (and the other
occurrences around the file) use the typed helper to keep return tuples/argument
shapes type-safe.

src/components/LatestBuild/LatestBuildSection.tsx (1)

18-19: Use path aliases for these internal imports.

These relative imports bypass the repo’s alias/layering convention and make moves/refactors noisier. Please switch them to ~/components/... imports.

As per coding guidelines: "Use absolute imports with configured path aliases: ~/components, ~/types, ~/k8s, ~/utils, ~/models, @routes"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/components/LatestBuild/LatestBuildSection.tsx` around lines 18 - 19, The
file LatestBuildSection.tsx uses relative imports for internal components
(CommitLabel and StatusIconWithTextLabel); replace the relative paths with the
project's path aliases (e.g., import CommitLabel from
'~/components/Commits/commit-label/CommitLabel' and import {
StatusIconWithTextLabel } from '~/components/StatusIcon/StatusIcon') so the
imports follow the repo convention and layering rules; update the import
statements referencing CommitLabel and StatusIconWithTextLabel accordingly and
run the TypeScript build to verify alias resolution.

src/components/LatestBuild/LatestBuildSection.tsx (1)

32-35: Consider simplifying the useMemo expression for readability.

The nested ternary with array access is functionally correct but somewhat dense. A more explicit form would improve maintainability.

♻️ Proposed refactor

 const commit = React.useMemo(
-  () => ((pipelineRunLoaded && pipelineRun && getCommitsFromPLRs([pipelineRun], 1)) || [])[0],
+  () => {
+    if (!pipelineRunLoaded || !pipelineRun) return undefined;
+    return getCommitsFromPLRs([pipelineRun], 1)?.[0];
+  },
   [pipelineRunLoaded, pipelineRun],
 );

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/components/LatestBuild/LatestBuildSection.tsx` around lines 32 - 35, The
useMemo for commit is hard to read due to a nested ternary/array access; rewrite
the React.useMemo callback to explicitly check pipelineRunLoaded and pipelineRun
first, call getCommitsFromPLRs([pipelineRun], 1) only when both are truthy, then
return the first element (or undefined) — i.e., refactor the current expression
that assigns commit to use a clearer if/guard style within the useMemo callback
while keeping the same dependency array ([pipelineRunLoaded, pipelineRun]) and
using getCommitsFromPLRs to extract the commit.