fix: error colour precedence in message wrapper

[JBR90]

Description

Type 'user' was overriding background colour of the chat message box for generic and moderation error messages on reload of the page.

• Change order of classes so errorType has precedence.

Issue(s) - AI-527

https://www.notion.so/oaknationalacademy/Sensitive-warnings-lose-colour-d1b3361edcf7478ea3b04f7be844a7ce

How to test

1. Go to https://oak-ai-lesson-assistant-p6i18zgf9.vercel-preview.thenational.academy
   Create a lesson with sensitive content, refresh the page, sensitive content box remains mint green colour

Checklist

• Manually tested across browsers / devices
• Considered impact on accessibility
• Does this PR update a package with a breaking change

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
oak-ai-lesson-assistant	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 10, 2024 4:13pm

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Playwright e2e tests

Job summary

Download report

To view traces locally, unzip the report and run:

npx playwright show-report ~/Downloads/playwright-report

[codeincontext]

Is this your first PR on the repo? If so, welcome!

I noticed that MessageWrapperProps has type: "user" | "editing" | "warning" | "moderation" | "aila";. Should the type be moderation rather than user?

[JBR90]

Is this your first PR on the repo? If so, welcome! -

Thanks!

I noticed that MessageWrapperProps has type: "user" | "editing" | "warning" | "moderation" | "aila";. Should the type be moderation rather than user?

The type for messages with the changing colour are user with errorType moderation

type: "user" | "editing" | "warning" | "moderation" | "aila";

errorType: "generic" | "moderation" | null;

Should they be coming through as type = moderation ?

[codeincontext]

type: "user"

Ah, I see. I didn't realise that it was user with errorType: "moderation. I think that's how it has always been, though I'm sure it could be improved if needed later. Maybe it has the moderation type when it first appears, but it gets persisted as user? I'll approve as the change you have here makes sense and solves the problem

[oak-machine-user]

🎉 This PR is included in version 1.8.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀