Replace infrastructure scanner error page with ErrorPage component#7338
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
c6f0efc to
a4aeaad
Compare
970a2cb to
c2ddebd
Compare
Greptile OverviewGreptile Summary
Confidence Score: 3/5
Important Files Changed
|
|
@greptile |
Additional Comments (1)
|
|
@greptile |
|
@greptile |
Additional Comments (1)
This effect will run any time Avoid depending on an unstable |
speaker-ender
left a comment
There was a problem hiding this comment.
Approving because it seems to function as intended.
I do have a concern about some of the logic as noted in my comment.
2982870 to
b9f08d1
Compare
Ticket ENG-2533
Description Of Changes
Replace the Chakra-based
ScannerErrorcomponent with the shared Ant DesignErrorPagecomponent across all infrastructure scanner forms. Migrate layout from Chakra (Stack,Box,HStack,Text) to Ant (Flex,Typography) and update toast notifications fromuseChakraToasttouseMessage.Code Changes
fullScreenprop toErrorPageto support inline (non-full-screen) usageErrorPageerror prop to acceptParsedErrorin addition to RTK error types, with anisParsedErrortype guarddefaultMessagehandling so it takes priority overerror.messageforParsedErrorwhen explicitly providedScannerErrorwithErrorPageinAuthenticateAwsForm,AuthenticateOktaForm, andLoadDataFlowScannerAuthenticateAwsFormLoadDataFlowScannerfromuseChakraToasttouseMessageisRequiredto Okta form fields that were missing itconstants.tsxScannerError.tsxSteps to Confirm
Pre-Merge Checklist
CHANGELOG.mdupdated