fix: only categorise initial user input once

[stefl]

Description

Back-end only, no user-facing change other than speeding up each message by a few seconds in the initial response time.

• We currently have a bug where we categorise the lesson plan each time we send a message
• This is because we were failing to call the aila.initialise() method consistently
• This add a private boolean flag to Aila to store that it has been initialised
• generate and generateAsync will throw if the instance has not been initialised
• Updates tests to call the initialise method
• Update the Aila test to ensure we only categorise empty lesson plans once
• We have this separate initialise method because it is async and cannot be called in the constructor (unless I am mistaken!)

How to test

• Run the dev server
• Start a new lesson
• See a log for aila:categorisation with the initial message as input
• Send another message
• No further aila:categorisation logs appear

[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	Nov 7, 2024 4:10pm

[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 test results

 14 passed
 1 skipped

Details

 Open report ↗︎
 15 tests across 14 suites
 1 minute, 59 seconds
 f866959

Skipped tests

No persona › tests/auth.test.ts › authenticate through Clerk UI

[codeincontext]

• We have this separate initialise method because it is async and cannot be called in the constructor (unless I am mistaken!)

That's an interesting distinction between a class and using a "regular" closure I hadn't considered

[codeincontext]

Great PR. I tested on the preview branch and it worked as expected

I suppose we would need to add an agent if the user wanted to change the key stage or subject later

[stefl]

Great PR. I tested on the preview branch and it worked as expected

I suppose we would need to add an agent if the user wanted to change the key stage or subject later

I think Aila might try to do its best if you try to change the entire title / subject / key stage but really the best approach there is to start a new lesson

[codeincontext]

Great PR. I tested on the preview branch and it worked as expected
I suppose we would need to add an agent if the user wanted to change the key stage or subject later

I think Aila might try to do its best if you try to change the entire title / subject / key stage but really the best approach there is to start a new lesson

I think as we change the UI around picking key stage that problem might go away anyway

[oak-machine-user]

🎉 This PR is included in version 1.14.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀