-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix config and view files tab underlines #4616
Conversation
bab4053
to
361b9e8
Compare
@@ -1,4 +1,5 @@ | |||
name: Generate kURL Add-On | |||
description: Generate kURL Add-On |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actionlint started failing because these were missing https://github.com/replicatedhq/kots/actions/runs/9069742713/job/24919992210
@@ -49,6 +49,7 @@ runs: | |||
|
|||
- uses: chainguard-images/actions/apko-publish@main | |||
with: | |||
apko-image: ghcr.io/wolfi-dev/apko@sha256:87b47283433066d19b71e1cb4401be8d04b7d51f4f4263fde1977c3043b9754f |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
resolves issue with latest
apko image https://github.com/replicatedhq/kots/actions/runs/9069367744/job/24919025968?pr=4616#step:3:140
What this PR does / why we need it:
This PR fixes an issue where the KOTS UI subnav would not show the selected tab for the "Config", "Troubleshoot", and "View Files" tabs. This is because previously we were only considering the last element in the path, so any routes with subpaths like
/config/<sequence>
or/troubleshoot/analyze/<bundle-id>
would cause the tabs to show as not active.Before
/app/craig-helm/tree/0
:After
/app/craig-helm/tree/0
:Which issue(s) this PR fixes:
Fixes https://app.shortcut.com/replicated/story/102653/config-and-view-files-tab-lack-blue-underline-when-clicked-on
Special notes for your reviewer:
Steps to reproduce
Does this PR introduce a user-facing change?
Does this PR require documentation?