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

Use react router's route handle functionality to remove duplicate containers #3481

Merged
merged 1 commit into from
Jul 1, 2024

Conversation

AlanGreene
Copy link
Member

Changes

#2452

Configure the resource GVK on the relevant routes to enable use of a common container for most resource list pages. This also means that a number of custom hooks are no longer required.

Ensure extensions work as expected in this new setup, correctly handling the namespace dropdown behaviour depending on whether the extension is for namespace-scoped or cluster-scoped resources.

Rename params in paths to use consistent naming, i.e. name should always be used for the resource name to allow for common code to process this centrally without the need for resource-specific handling.

/kind misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (new features, significant UI changes, API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

…tainers

Configure the resource GVK on the relevant routes to enable use of a common
container for most resource list pages. This also means that a number of
custom hooks are no longer required.

Ensure extensions work as expected in this new setup, correctly handling
the namespace dropdown behaviour depending on whether the extension is for
namespace-scoped or cluster-scoped resources.

Rename params in paths to use consistent naming, i.e. `name` should always
be used for the resource name to allow for common code to process this
centrally without the need for resource-specific handling.
@tekton-robot tekton-robot added kind/misc Categorizes issue or PR as a miscellaneuous one. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jun 29, 2024
@AlanGreene AlanGreene removed the request for review from skaegi June 29, 2024 12:57
Copy link
Contributor

@briangleeson briangleeson left a comment

Choose a reason for hiding this comment

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

/lgtm

Looks good, and nice bit of code reduction too

@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: briangleeson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 1, 2024
@tekton-robot tekton-robot merged commit 8dd9da2 into tektoncd:main Jul 1, 2024
7 of 8 checks passed
@AlanGreene AlanGreene deleted the containers_simplify branch July 1, 2024 11:26
@AlanGreene
Copy link
Member Author

This resolves most of the blockers for #3381

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants