WIP - add email confirmation

[swdpcomputing]

No description provided.

[swdpcomputing]

[Andrew-Folga]

Is this following the FCP container guidelines from here: https://defra.github.io/ffc-development-guide/development-patterns/containers/

We can introduce a new local docker compose config but there is already a dedicated docker-compose.override.yaml. WDYT?

[swdpcomputing]

I am following as far as I understand it. Happy to discuss.

[Andrew-Folga]

As discussed yesterday let's merge it with the override one if possible.

[Andrew-Folga]

This is needed for ARM based architectures - why are we removing it here?

[swdpcomputing]

It's been replaced.

[Andrew-Folga]

Same as above - why do we need separate docker compose config for local env - we already have the override config?

[swdpcomputing]

Because the override is being run in sandbox, and we want to keep this only running on local machines.

[Andrew-Folga]

Override is being run in both local and sandbox - there should be no local docker to avoid duplication.

[Andrew-Folga]

I think there might have been an error during a rebase from main. We no longer have src/config/app.js but instead we have src/config/app/app-config.js.

[swdpcomputing]

ah ok. Will adjust

[Andrew-Folga]

XState has a dedicated services section for invoking long-running, asynchronous tasks (e.g., API calls, database queries, timers, etc.). Actions, on the other hand, are used for synchronous operations like logging, updating the context, or emitting additional events.

Use Services:

1. For long-running tasks that need asynchronous handling (e.g., API calls, timers).
2. When the task needs to determine the next state based on its success or failure.

Use Actions:

1. For synchronous operations like logging, updating the context, or emitting additional events.
2. When the operation doesn’t determine the next state.

Here is a useful table:

Aspect	Services	Actions
Purpose	Handle asynchronous, potentially long-running tasks.	Perform side effects or execute logic during state transitions.
Execution Timing	Triggered when the machine enters a specific state (via invoke) or manually using send.	Executed immediately during state transitions or on events.
Return Value	Returns a promise or observable, used to determine the next state (onDone, onError).	Returns nothing; performs tasks like logging, updating context, or dispatching events.
Integration	Associated with states via invoke.	Defined directly in actions and used in state transitions.

See: https://xstate.js.org/docs/guides/communication.html#the-invoke-property

[Andrew-Folga]

Could we get a small README section if relevant to mention few words about this new config? WDYT?

[Andrew-Folga]

Just wondering whether we want to check in IDE specific files hmm.

[sonarcloud]

Quality Gate failed

Failed conditions
1 New Critical Issues (required ≤ 0)
1 New Major Issues (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE