-
Notifications
You must be signed in to change notification settings - Fork 705
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
Remove most references to shared/ResourceRef #3887
Conversation
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.
Excellent!! It's great we are removing so much logic from the UI. Now it looks much better! Thanks for the clean-up!
@@ -22,10 +19,4 @@ function mapStateToProps({ kube }: IStoreState, props: IAccessURLTableContainerP | |||
}; | |||
} |
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.
Not necessarily in this PR, but we should also get rid of the xxxxContainer.tsx in favor of just using react hooks, especially, now we have removed more logic
79bd8a4
to
ab8ef43
Compare
Signed-off-by: Michael Nelson <minelson@vmware.com>
Signed-off-by: Michael Nelson <minelson@vmware.com>
Signed-off-by: Michael Nelson <minelson@vmware.com>
Signed-off-by: Michael Nelson <minelson@vmware.com>
da886ee
to
c1e2820
Compare
* Extract more unused actions. Signed-off-by: Michael Nelson <minelson@vmware.com> * Prettier Signed-off-by: Michael Nelson <minelson@vmware.com> * Remove no-longer-used test code. Signed-off-by: Michael Nelson <minelson@vmware.com>
Description of the change
When the dashboard was handling the fetching of resources directly from the k8s api server, it needed to also keep state about whether resources were namespaced, url endpoints for the resources and a bunch of other book-keeping. This is no longer necessary for the dashboard.
This PR begins the work of extracting the ResourceRef model, by removing it from the AppView and corresponding components/containers, and doing a drop-in replacement with the simpler generated ResourceRef from our protobuf message.
Benefits
Less code to maintain, simpler dashboard.
Possible drawbacks
Applicable issues
Additional information