Skip to content
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

feat: enhance Ingress details view #3205

Merged
merged 5 commits into from
Aug 22, 2024

Conversation

OliwiaGowor
Copy link
Contributor

@OliwiaGowor OliwiaGowor commented Aug 20, 2024

Description

Changes proposed in this pull request:

  • enhance Ingress details view
  • adjust tests

Related issue(s)
Closes #3067

Definition of done

  • The PR's title starts with one of the following prefixes:
    • feat: A new feature
    • fix: A bug fix
    • docs: Documentation only changes
    • refactor: A code change that neither fixes a bug nor adds a feature
    • test: Adding tests
    • chore: Maintainance changes to the build process or auxiliary tools, libraries, workflows, etc.
  • Related issues are linked. To link internal trackers, use the issue IDs like backlog#4567
  • Explain clearly why you created the PR and what changes it introduces
  • All necessary steps are delivered, for example, tests, documentation, merging

@kyma-bot kyma-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 20, 2024
@kyma-bot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kyma-bot kyma-bot added cla: yes Indicates the PR's author has signed the CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Aug 20, 2024
@OliwiaGowor OliwiaGowor marked this pull request as ready for review August 21, 2024 13:01
@kyma-bot kyma-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 21, 2024
t('ingresses.labels.secret-name'),
]}
rowRenderer={tls => [
tls?.hosts?.join(', ') ?? EMPTY_TEXT_PLACEHOLDER,
Copy link
Contributor

Choose a reason for hiding this comment

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

I think it would make sense to use the <Tokens> component here instead of joining strings

});

setHealthyPods(healthyPods);
};
Copy link
Contributor

@chriskari chriskari Aug 22, 2024

Choose a reason for hiding this comment

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

we can merge these two methods, using a single loop for both

also, is the naming pods vs. ports intended?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, it was a typo :)

cy.getMidColumn()
.contains(/tls/i)
.should('be.visible');

Copy link
Contributor

Choose a reason for hiding this comment

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

you could add a check if the given hosts and secretName are displayed correctly :)

),
},
customContent: [
...(ingress.hostname
Copy link
Contributor

Choose a reason for hiding this comment

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

as far as I see we can remove those spread operators here and below and simply not place the resulting object inside of an array

{`${t('ingresses.labels.host-name')}:`}
</span>
{`${ingress.hostname}`}
</div>
Copy link
Contributor

Choose a reason for hiding this comment

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

can we replace this somehow with a UI5 component?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think so, that's how we are doing it in metadata and status - Labels have slightly different color

@kyma-bot kyma-bot added the lgtm Looks good to me! label Aug 22, 2024
@kyma-bot kyma-bot merged commit 21cd854 into kyma-project:main Aug 22, 2024
13 checks passed
@OliwiaGowor OliwiaGowor deleted the adjust-ingress branch September 16, 2024 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Indicates the PR's author has signed the CLA. lgtm Looks good to me! size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enhance Ingress details view
4 participants