Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Unités] Pouvoir créer une mission à partir d'une unité #2815

Merged
merged 69 commits into from
Feb 21, 2024

Conversation

@ivangabriele ivangabriele force-pushed the ivan/add-new-mission-button-in-control-unit-card branch 8 times, most recently from aff481b to a8a3edc Compare January 16, 2024 09:56
@ivangabriele ivangabriele marked this pull request as ready for review January 16, 2024 13:00
@ivangabriele ivangabriele force-pushed the ivan/add-new-mission-button-in-control-unit-card branch from 78c6e36 to 63e7470 Compare January 16, 2024 15:49
@ivangabriele ivangabriele force-pushed the ivan/add-new-mission-button-in-control-unit-card branch from 5840731 to 70e480c Compare January 24, 2024 08:20
@ivangabriele ivangabriele force-pushed the ivan/add-new-mission-button-in-control-unit-card branch 3 times, most recently from cb52072 to 6d2fb3f Compare February 9, 2024 07:49
@ivangabriele ivangabriele added the feat. enhancement feature enhancement label Feb 10, 2024
@ivangabriele ivangabriele force-pushed the ivan/add-new-mission-button-in-control-unit-card branch from ef344e2 to 43dac9a Compare February 12, 2024 16:56
@ivangabriele ivangabriele force-pushed the ivan/add-new-mission-button-in-control-unit-card branch from 4a614d3 to 6ed294f Compare February 13, 2024 00:54
frontend/src/domain/entities/sideWindow/types.ts Outdated Show resolved Hide resolved
frontend/src/domain/use_cases/error/displayOrLogError.ts Outdated Show resolved Hide resolved
frontend/src/domain/use_cases/error/displayOrLogError.ts Outdated Show resolved Hide resolved
frontend/src/domain/use_cases/error/retry.ts Outdated Show resolved Hide resolved
export const openSideWindowPath =
(path: SideWindow.Path, withoutConfirmation: boolean = false): MainAppThunk =>
async (dispatch, getState) => {
const { missionForm, sideWindow } = getState()
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ce type de destruct est assez peu performant je crois, autant faire un getState().missionForm

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alors là contrairement au useSelector() c'est vraiment la même chose car le dispatcher n'est pas un hook qui subscribe. Ce n'est exécuté qu'une fois lorsqu'on l'appelle. La fonction getState() est exécutée et le store est renvoyé dans son ensemble quoique tu fasses. Même la déstrusturation en elle-même n'a un aucun impact de perf en elle-même dans ce cas car c'est un retour de fonction donc dans les deux cas 2 nouvelles valeurs en mémoire.

frontend/src/features/VesselSidebar/Body.tsx Outdated Show resolved Hide resolved
frontend/src/libs/PendingUseCase.ts Outdated Show resolved Hide resolved
@ivangabriele ivangabriele force-pushed the ivan/add-new-mission-button-in-control-unit-card branch 3 times, most recently from 310326d to 2898d62 Compare February 15, 2024 23:40
Copy link
Collaborator

@louptheron louptheron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ça me parait bien avec l'utilisation de import-meta-env, on peut par contre préciser que les envs infra servent juste à faire tourner les images docker je pense. Je trouve qu'en l'état on ne sait pas quel env est lié à quoi, car on a de envs dans /fontend, dans /infra/configurations, dans /infra/.env.*

infra/.env.local.defaults Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
infra/docker/app/env.sh Outdated Show resolved Hide resolved
timeout: 1s
retries: 30

monitorenv_flyway:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on peut enlever flyway - cf. le docker-compose puppeteer

Copy link
Member Author

@ivangabriele ivangabriele Feb 21, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A voir dans la PR de déplacement de /docker-compose.yml vers /infra/docker/docker-compose.yml.

@ivangabriele ivangabriele force-pushed the ivan/add-new-mission-button-in-control-unit-card branch from eff8749 to 32ce9af Compare February 21, 2024 14:12
@ivangabriele ivangabriele force-pushed the ivan/add-new-mission-button-in-control-unit-card branch from 32ce9af to 69127d9 Compare February 21, 2024 14:16
@ivangabriele ivangabriele force-pushed the ivan/add-new-mission-button-in-control-unit-card branch 4 times, most recently from ead2847 to e8c4fdb Compare February 21, 2024 19:24
@ivangabriele ivangabriele force-pushed the ivan/add-new-mission-button-in-control-unit-card branch from e8c4fdb to 72093cd Compare February 21, 2024 19:58
Copy link

sonarcloud bot commented Feb 21, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@ivangabriele ivangabriele merged commit 6b95923 into master Feb 21, 2024
27 checks passed
@ivangabriele ivangabriele deleted the ivan/add-new-mission-button-in-control-unit-card branch February 21, 2024 23:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment