-
Notifications
You must be signed in to change notification settings - Fork 12
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
Show error on kubernetes pages and kubernetes endpoint page. #96
Conversation
Codecov Report
@@ Coverage Diff @@
## v2-master #96 +/- ##
============================================
+ Coverage 71.89% 71.9% +0.01%
============================================
Files 685 686 +1
Lines 29586 29632 +46
Branches 6789 6811 +22
============================================
+ Hits 21271 21308 +37
- Misses 8315 8324 +9 |
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.
Looks good, once we get it passed gates this can be merged
const clearedEntity = Object.keys(entityState).reduce((prevEntityState, key) => { | ||
return { | ||
...prevEntityState, | ||
[key]: defaultPaginationEntityState |
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.
Regarding the previous code.. when we come back to this in the future we should just remove the entry instead of resetting.
- extend time for create service instance tests - extend time for some user tests (don't think this will help as much as SI) - ensure we don't fail when a service we don't want to be there doesn't
a60060d
to
e514c58
Compare
Made new smaller effect that gets all error wrapper events and throws an internal error based on some new config.
I've also changed the routing path variable to be common across kubernetes and cf pages to make it easier for the page header to automatically pickup endpoint error states.