-
Notifications
You must be signed in to change notification settings - Fork 7.9k
render components based on the annotations #21180
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
Conversation
1 flaky tests on run #8132 ↗︎Details:
|
|||||||||||||||||||||
| Test | Artifacts | |
|---|---|---|
| Authentication test > should add a condition |
Output
Screenshots
|
|
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.
9472ccb to
88ed041
Compare
| Object.entries(annotations || {}).map(([key, value]) => ({ | ||
| key, | ||
| value, | ||
| value: value as Record<string, unknown>, |
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.
Looking at the type, it is the same as the one it is being cast to. So I think we can omit this cast.
| value: value as Record<string, unknown>, | |
| value, |
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.
the build failed when it was omitted
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.
Ahhh, I see. I didn't re-build the admin client, so I never got the new type.
* render components based on the annotations * merge fix
Co-authored-by: Erik Jan de Wit <[email protected]>
At the moment this only addresses the admin UI, but planned is to refactor this into a common components that work as well for the account ui
fixes: #20837