You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
## Issue description
Correct the typo in the changeset summary so it doesn't appear in release notes.
## Fix Focus Areas
- workspaces/orchestrator/.changeset/new-books-matter.md[1-5]
## Suggested fix
Change "worfkflow" to "workflow".
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
2. MUI v4/v5 Alert mix 🐞≡
Description
WorkflowResult now uses Alert/AlertTitle from @material-ui/lab (MUI v4) alongside @mui/material (MUI
v5) components, which can bypass the host’s MUI v5 theme context and cause inconsistent styling/CSS
injection order issues. The PR also adds @material-ui/lab as a runtime dependency, increasing the
likelihood of duplicated styling stacks within the same plugin.
+import { Alert, AlertTitle } from '@material-ui/lab';
import Box from '@mui/material/Box';
import Button from '@mui/material/Button';
import CircularProgress from '@mui/material/CircularProgress';
Relevance
⭐ Low
Mixing MUI v4/v5 is already present/accepted for UI fixes; this PR intentionally uses v4 lab Alert.
ⓘ Recommendations generated based on similar findings in past PRs
Evidence
WorkflowResult mixes MUI v4 lab Alert with MUI v5 components, while the plugin otherwise uses MUI v5
Alert and MUI v5 theme hooks (dark mode detection). The package explicitly peers on @mui/material
(v5) but now pulls in @material-ui/lab (v4) as a direct dependency, creating a split
component/theming setup inside the same package.
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
## Issue description
`WorkflowResult` switched from MUI v5 `@mui/material/Alert` to MUI v4 `@material-ui/lab` `Alert`, while the rest of the plugin uses MUI v5 components and the MUI v5 theme context. This can lead to theme mismatch (not picking up dark-mode palette), inconsistent styling, and extra CSS-in-JS engine interactions.
## Issue Context
The package declares `@mui/material` as a peer dependency and uses `@mui/material/styles` (`useTheme`) elsewhere; introducing `@material-ui/lab` (v4) splits the UI stack.
## Fix Focus Areas
- workspaces/orchestrator/plugins/orchestrator/src/components/WorkflowInstancePage/WorkflowResult.tsx[21-36]
- workspaces/orchestrator/plugins/orchestrator/package.json[69-85]
## Suggested fix
1. Prefer reverting `WorkflowResult` to `@mui/material/Alert` and `@mui/material/AlertTitle`.
2. If the intent is to defeat host theme overrides, apply higher-specificity styling to the v5 Alert instead (e.g., `sx={{ '&&': { ... } }}` / `classes` / `styled()`), rather than switching component libraries.
3. Remove `@material-ui/lab` from dependencies if it becomes unused.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
ⓘ The new review experience is currently in Beta. Learn more
• Added flexbox styling to DialogTitle Box component
• Implements flex layout with baseline alignment and space-between justification
• Improves visual alignment of title and close button
View more (2) 4. workspaces/orchestrator/plugins/orchestrator/src/components/WorkflowInstancePage/WorkflowResult.tsx
🐞 Bug fix +3/-4
Fix Alert imports and increase Divider specificity
• Replaced Material-UI v5 Alert and AlertTitle with v4 lab versions
• Increased CSS specificity for Divider components using && selector
• Changed margin properties from mb: 2 and mt: 2, mb: 2 to use && wrapper
• Increased CSS specificity for root styles using && selector
• Moved backgroundColor and outline properties into specificity wrapper
• Prevents theme and MUI defaults from overriding component styling
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey, I just made a Pull Request!
https://redhat.atlassian.net/browse/RHDHBUGS-2967
Fix orchestrator UI styling overrides:
TextCodeBlockPaper background/outline and forWorkflowResultAlertfor result messages where v5 class naming conflicted with the shell theme.Before fix:
After fix:
Steps to test:
1.Start the RHDH app with the following dark theme config:
✔️ Checklist