Skip to content

Comments

fix(KFLUXUI-1076): set correct url for list of issues#718

Open
JoaoPedroPP wants to merge 1 commit intokonflux-ci:mainfrom
konflux-jp-repos:KFLUXUI-1076
Open

fix(KFLUXUI-1076): set correct url for list of issues#718
JoaoPedroPP wants to merge 1 commit intokonflux-ci:mainfrom
konflux-jp-repos:KFLUXUI-1076

Conversation

@JoaoPedroPP
Copy link
Member

@JoaoPedroPP JoaoPedroPP commented Feb 23, 2026

Assisted-by: Cursor

Fixes

KFLUXUI-1076

Description

Set correct URL for View all issues link in LatestIssuesCard component.

Type of change

  • Feature
  • Bugfix
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

Screen shots / Gifs for design review

Before
image

After
image

How to test or reproduce?

  1. Click on Issues side menu
  2. In the "Latest Issues" card, click on View all issues link
  3. You should be redirect to the list of issues(It's ok to be empty but 404 shouldn't be there)

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

Summary by CodeRabbit

  • Bug Fixes

    • Fixed "View all issues" button so it correctly opens the issues list for the current workspace/namespace.
  • Tests

    • Updated tests to reflect the workspace-scoped issues list routing.

@JoaoPedroPP JoaoPedroPP requested a review from a team as a code owner February 23, 2026 19:57
@JoaoPedroPP JoaoPedroPP requested review from marcin-michal and sahil143 and removed request for a team February 23, 2026 19:57
@snyk-io
Copy link
Contributor

snyk-io bot commented Feb 23, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 23, 2026

Note

.coderabbit.yaml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)
Validation error: Unrecognized key(s) in object: 'version', 'include', 'exclude', 'rules', 'limits'
⚙️ Configuration instructions
  • Please see the configuration documentation for more information.
  • You can also validate your configuration using the online YAML validator.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
📝 Walkthrough

Walkthrough

Replaced a hard-coded "/issues/list" link in LatestIssuesCard with ISSUES_LIST_PATH.createPath({ workspaceName: namespace }) and updated corresponding tests to expect the namespace-scoped route.

Changes

Cohort / File(s) Summary
LatestIssuesCard component
src/components/Issues/LatestIssuesCard.tsx
Imported ISSUES_LIST_PATH and changed the "View all issues" link to use ISSUES_LIST_PATH.createPath({ workspaceName: namespace }) instead of the hard-coded /issues/list.
Tests (namespace routing)
src/components/Issues/__tests__/LatestIssuesCard.spec.tsx
Updated assertions to expect the namespace-scoped path (/ns/test-namespace/issues/list) in three locations to match the component change.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5-10 minutes

Possibly related PRs

Suggested reviewers

  • sahil143
  • marcin-michal
  • rakshett

Poem

A tiny link finds its place, namespace in tow,
From static road to pathways that grow.
Tests adjust their steady gaze,
Paths now sing in scoped arrays —
Small change, smooth flow. 🎉

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: fixing the URL for the 'View all issues' link in LatestIssuesCard by using namespace-scoped routing instead of a hard-coded path.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

milantaky
milantaky previously approved these changes Feb 23, 2026
Copy link
Member

@milantaky milantaky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Set correct URL for `View all issues` link in LatestIssuesCard
component.

Jira KFLUXUI-1076

Assisted-by: Cursor
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

♻️ Duplicate comments (1)
src/components/Issues/__tests__/LatestIssuesCard.spec.tsx (1)

388-388: Same path-hardcoding concern as above.
Please apply the route-helper refactor here as well.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/components/Issues/__tests__/LatestIssuesCard.spec.tsx` at line 388,
Replace the hard-coded href assertion for viewAllLink with the route-helper used
elsewhere: instead of asserting '/ns/test-namespace/issues/list', call the
shared route builder (e.g., getIssuesListPath or buildIssuesListRoute) with the
test namespace value and assert that the resulting string is the href; update
the expect on viewAllLink to use that helper so paths stay consistent with other
tests and routing changes.
🧹 Nitpick comments (1)
src/components/Issues/__tests__/LatestIssuesCard.spec.tsx (1)

149-149: Use the route helper in the test to avoid hard-coded paths.

Align the assertion with production routing by using ISSUES_LIST_PATH.createPath(...) so future path changes don’t require multiple test updates.

♻️ Suggested change
+import { ISSUES_LIST_PATH } from '~/routes/paths';
-      expect(viewAllLink).toHaveAttribute('href', '/ns/test-namespace/issues/list');
+      expect(viewAllLink).toHaveAttribute(
+        'href',
+        ISSUES_LIST_PATH.createPath({ workspaceName: 'test-namespace' }),
+      );
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/components/Issues/__tests__/LatestIssuesCard.spec.tsx` at line 149,
Replace the hard-coded href assertion with the route helper: import
ISSUES_LIST_PATH and use expect(viewAllLink).toHaveAttribute('href',
ISSUES_LIST_PATH.createPath({ namespace: 'test-namespace' })); this ensures the
test uses the same route generation as production and avoids brittle string
literals (update imports in LatestIssuesCard.spec.tsx to include
ISSUES_LIST_PATH if missing).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@src/components/Issues/__tests__/LatestIssuesCard.spec.tsx`:
- Line 388: Replace the hard-coded href assertion for viewAllLink with the
route-helper used elsewhere: instead of asserting
'/ns/test-namespace/issues/list', call the shared route builder (e.g.,
getIssuesListPath or buildIssuesListRoute) with the test namespace value and
assert that the resulting string is the href; update the expect on viewAllLink
to use that helper so paths stay consistent with other tests and routing
changes.

---

Nitpick comments:
In `@src/components/Issues/__tests__/LatestIssuesCard.spec.tsx`:
- Line 149: Replace the hard-coded href assertion with the route helper: import
ISSUES_LIST_PATH and use expect(viewAllLink).toHaveAttribute('href',
ISSUES_LIST_PATH.createPath({ namespace: 'test-namespace' })); this ensures the
test uses the same route generation as production and avoids brittle string
literals (update imports in LatestIssuesCard.spec.tsx to include
ISSUES_LIST_PATH if missing).

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c189941 and 0ceb19f.

📒 Files selected for processing (2)
  • src/components/Issues/LatestIssuesCard.tsx
  • src/components/Issues/__tests__/LatestIssuesCard.spec.tsx
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/components/Issues/LatestIssuesCard.tsx

@codecov
Copy link

codecov bot commented Feb 23, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.12%. Comparing base (d8a8dde) to head (0ceb19f).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #718      +/-   ##
==========================================
- Coverage   87.23%   87.12%   -0.12%     
==========================================
  Files         764      764              
  Lines       58225    58228       +3     
  Branches     5658     5658              
==========================================
- Hits        50795    50731      -64     
- Misses       7376     7419      +43     
- Partials       54       78      +24     
Flag Coverage Δ
e2e 45.70% <ø> (-4.39%) ⬇️
unittests 85.80% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
src/components/Issues/LatestIssuesCard.tsx 100.00% <100.00%> (ø)

... and 39 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d8a8dde...0ceb19f. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Member

@rrosatti rrosatti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants