Skip to content

Refactor mission crew#1107

Open
lwih wants to merge 1 commit into
mainfrom
refactor-mission-crew
Open

Refactor mission crew#1107
lwih wants to merge 1 commit into
mainfrom
refactor-mission-crew

Conversation

@lwih

@lwih lwih commented Dec 17, 2025

Copy link
Copy Markdown
Collaborator

No description provided.

@tristanrobert

tristanrobert commented Dec 17, 2025

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@lwih lwih force-pushed the refactor-mission-crew branch from 104d112 to 859dc31 Compare January 19, 2026 17:54
@github-actions

github-actions Bot commented Jan 19, 2026

Copy link
Copy Markdown
Contributor

Coverage Report for frontend

Status Category Percentage Covered / Total
🔵 Lines 66.16% (🎯 40%) 3264 / 4933
🔵 Statements 64.43% (🎯 40%) 3479 / 5399
🔵 Functions 56.32% (🎯 40%) 1127 / 2001
🔵 Branches 58.61% (🎯 40%) 1470 / 2508
File Coverage
File Stmts Branches Functions Lines Uncovered Lines
Changed Files
frontend/src/features/common/components/ui/custom-dialog.tsx 100% 100% 100% 100%
frontend/src/v2/features/common/components/ui/formik-date-range-picker.tsx 100% 100% 100% 100%
frontend/src/v2/features/common/schemas/dates-schema.ts 100% 100% 100% 100%
frontend/src/v2/features/common/types/crew-type.ts 100% 100% 100% 100%
frontend/src/v2/features/common/types/mission-types.ts 100% 100% 100% 100%
frontend/src/v2/features/mission-general-infos/components/mission-general-information-crew-no-comment.tsx 33.33% 33.33% 8.33% 46.15% 34, 35, 38-39, 53-98
frontend/src/v2/features/mission-general-infos/ui/mission-crew-form-no-comment.tsx 20% 0% 0% 26.31% 19-23, 25-30, 33-34, 39-50, 69-125
frontend/src/v2/features/mission-general-infos/ui/mission-crew-list-no-comment.tsx 25% 100% 0% 25% 20-29
frontend/src/v2/features/mission-general-infos/ui/mission-crew-list.tsx 100% 87.5% 100% 100%
frontend/src/v2/features/pam/components/element/general-info/mission-general-information-form-pam.tsx 100% 100% 100% 100%
frontend/src/v2/features/pam/components/element/general-info/mission-general-information-pam-body.tsx 71.42% 50% 50% 66.66% 15, 19
frontend/src/v2/features/pam/components/element/general-info/crew/crew-absence-form.tsx 68% 72.72% 64.28% 73.33% 56, 72-90, 96, 171
frontend/src/v2/features/pam/components/element/general-info/crew/crew-full-mission-absence-form.tsx 100% 100% 100% 100%
frontend/src/v2/features/pam/components/element/general-info/crew/crew-temporary-absence-form-item.tsx 100% 100% 83.33% 100%
frontend/src/v2/features/pam/components/element/general-info/crew/mission-general-information-crew-pam-absence-modal.tsx 100% 100% 100% 100%
frontend/src/v2/features/pam/components/element/general-info/crew/mission-general-information-crew-pam.tsx 74.46% 70.37% 81.25% 75.55% 59-79, 203-205
frontend/src/v2/features/pam/components/element/general-info/passengers/mission-general-information-passenger-pam.tsx 54.16% 76.19% 70% 56.52% 35-55, 140-141
frontend/src/v2/features/pam/components/ui/crew-absence-tag.tsx 100% 100% 100% 100%
frontend/src/v2/features/pam/components/ui/mission-crew-list-item-pam.tsx 100% 84.31% 100% 100%
frontend/src/v2/features/pam/components/ui/mission-passenger-list-item-pam.tsx 100% 100% 100% 100%
frontend/src/v2/features/pam/hooks/use-crew-absence-form.tsx 100% 100% 100% 100%
frontend/src/v2/features/pam/hooks/use-crew-absence-reason.tsx 100% 100% 100% 100%
frontend/src/v2/features/pam/hooks/use-crew-absence.tsx 100% 83.33% 100% 100%
frontend/src/v2/features/pam/hooks/use-pam-mission-general-information-form.tsx 84.84% 83.33% 88.23% 87.09% 31-36, 47-48
frontend/src/v2/features/pam/hooks/use-passenger-form.tsx 100% 100% 100% 100%
Generated in workflow #4508 for commit 41b6ebc by the Vitest Coverage Report Action

@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Jan 19, 2026
@lwih lwih force-pushed the refactor-mission-crew branch 2 times, most recently from c224e35 to 829228b Compare January 21, 2026 14:10
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Jan 21, 2026
@lwih lwih force-pushed the refactor-mission-crew branch from 829228b to c989e8b Compare January 21, 2026 14:57
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Jan 21, 2026
@lwih lwih force-pushed the refactor-mission-crew branch from c989e8b to 49aad89 Compare January 22, 2026 09:46
@lwih lwih marked this pull request as ready for review January 22, 2026 15:40
@lwih lwih force-pushed the refactor-mission-crew branch 2 times, most recently from 612670e to 4872ee4 Compare January 28, 2026 12:05
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Jan 28, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Jan 28, 2026
@lwih lwih force-pushed the refactor-mission-crew branch 4 times, most recently from c2d9097 to ea2c567 Compare February 5, 2026 15:03
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Feb 12, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Feb 12, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Feb 12, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Feb 12, 2026
@lwih lwih force-pushed the refactor-mission-crew branch from ea2c567 to 753e6ea Compare February 12, 2026 09:54
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Feb 12, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Feb 12, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Feb 12, 2026
@lwih lwih force-pushed the refactor-mission-crew branch 3 times, most recently from 01e9c3d to 1652f46 Compare February 16, 2026 18:05
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Feb 25, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Feb 25, 2026
@lwih lwih force-pushed the refactor-mission-crew branch 3 times, most recently from 1ee9656 to 8014c5b Compare February 25, 2026 10:11
@github-actions

Copy link
Copy Markdown
Contributor
Overall Project 76.07% -0.79%
Files changed 21.18%

File Coverage
GetCrewByServiceId.kt 100% 🍏
MissionCrew.kt 76.54% -9.23%
JPAMissionCrewRepository.kt 66% 🍏
MissionCrewModel.kt 65% -9.5%
MissionCrewEntity.kt 59.04% -18.08%
ExportMissionPatrolSingle.kt 1.71% -2.23%
MissionCrewAbsenceModel.kt 0%
MissionCrewAbsenceEntity.kt 0% -94.39%
MissionCrewAbsence.kt 0% -97.27%

@lwih lwih requested a review from xtiannyeto February 25, 2026 10:26
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Feb 25, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Feb 25, 2026
Comment on lines +24 to +27
var startDate: LocalDate? = null,

@Column(name = "end_date", nullable = true)
var endDate: LocalDate? = null,

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

je me demande si je suis pas un peu trop souple sur les dates

BEGIN
CREATE TABLE IF NOT EXISTS public.mission_crew_absence (
id SERIAL PRIMARY KEY,
mission_crew_id INTEGER NOT NULL REFERENCES public.mission_crew(id) ON DELETE CASCADE,

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

La table Absence est liée à la table MissionCrew avec un delete cascade.
En théorie, on ne delete pas de row de MissionCrew donc le delete cascade est pas si dangereux mais est ce que pour des soucis d'archivage, il faudrait pas mieux virer le delete cascade ? T'as un avis ?

Comment on lines +5 to +11
export function useMissionDates(missionId?: string): [string | undefined, string | undefined] {
const queryClient = useQueryClient()

const mission: Mission2 | undefined = missionId ? queryClient.getQueryData(missionsKeys.byId(missionId)) : undefined

return [mission?.data?.startDateTimeUtc, mission?.data?.endDateTimeUtc]
}

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Ici dans le frontend, après avoir déjà codé ce fichier, j'ai vu que t'as un use-mission avec quelques utils dedans. T'as un avis entre laisser ce hook ou le migrer dans use-mission ?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

on peut merger plus tard

Comment on lines +43 to +52
// if a temporary absence matches the whole length of the mission
// set it as full mission absence instead of just temporary
const isAbsentFullMission =
value.isAbsentFullMission ||
(missionStartDateTimeUtc &&
missionEndDateTimeUtc &&
startDate &&
endDate &&
isSameDay(new Date(startDate), new Date(missionStartDateTimeUtc)) &&
isSameDay(new Date(endDate), new Date(missionEndDateTimeUtc)))

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

ça, ça pourrait être fait dans le backend aussi

fieldArray: FieldArrayRenderProps
}

const MissionGeneralInformationCrewPam: React.FC<MissionGeneralInformationCrewPamProps> = ({

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Ce fichier il a pas vraiment changé mais au lieu d'un move, git m'a fait un delete/create

Comment on lines +37 to +47
// Local state for "new/unsaved" temporary absences
// Initialize with one empty absence so the user sees a form immediately
const [localAbsences, setLocalAbsences] = useState<MissionCrewAbsence[]>(absences.length === 0 ? [EMPTY_ABSENCE] : [])

// Track validity and values for each form row
const formStatesRef = React.useRef<Record<number, FormState>>({})
const [, forceUpdate] = useState(0)

// Display absences: committed ones first, then local ones
const displayAbsences = [...absences, ...localAbsences]

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

J'ai bien galéré avec Formik pour gérer des form temporaraires dans d'autres components dans des Modal

Comment on lines +62 to +67
const allFormsValid =
displayAbsences.length > 0 &&
displayAbsences.every((_, index) => {
const state = formStatesRef.current[index]
return state?.isValid === true
})

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Pour disable le bouton "valider" dans la modal si une des form rows est pas valide

@lwih lwih force-pushed the refactor-mission-crew branch 3 times, most recently from 82e9918 to a3aba6f Compare March 2, 2026 18:52
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Mar 3, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Mar 3, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Mar 3, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Mar 3, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Mar 3, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Mar 3, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Mar 3, 2026
@MTES-MCT MTES-MCT deleted a comment from github-actions Bot Mar 3, 2026
@lwih lwih force-pushed the refactor-mission-crew branch from 40dc21d to 543876a Compare March 9, 2026 11:48
crewModel.agent = agent
}
// if (crew.agent != null && crew.agent.id != null) {
// val agent = dbAgentRepository.findById(crew.agent.id).orElseThrow()

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Remove comments

DO
$$
BEGIN
CREATE TABLE IF NOT EXISTS public.mission_crew_absence (

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

naming, peut etre juste crew_absence

Comment on lines +5 to +11
export function useMissionDates(missionId?: string): [string | undefined, string | undefined] {
const queryClient = useQueryClient()

const mission: Mission2 | undefined = missionId ? queryClient.getQueryData(missionsKeys.byId(missionId)) : undefined

return [mission?.data?.startDateTimeUtc, mission?.data?.endDateTimeUtc]
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

on peut merger plus tard

@github-actions

Copy link
Copy Markdown
Contributor
Overall Project 79.8% -0.74%
Files changed 22.58%

File Coverage
GetCrewByServiceId.kt 100% 🍏
GetAgentsCrewByMissionId.kt 100% 🍏
MissionCrew.kt 76.26% -9.34%
JPAMissionCrewRepository.kt 65.97% -8.33%
MissionCrewModel.kt 65.46% -9.79%
MissionCrewEntity.kt 58.1% -17.39%
ExportMissionPatrolSingle.kt 1.05% -2.24%
MissionCrewAbsenceModel.kt 0%
MissionCrewAbsenceEntity.kt 0%
MissionCrewAbsence.kt 0%
AddOrUpdateMissionCrew.kt 0% -45.45%

@github-actions

Copy link
Copy Markdown
Contributor
# npm audit report

form-data  4.0.0 - 4.0.5
Severity: high
form-data: CRLF injection in form-data via unescaped multipart field names and filenames - https://github.com/advisories/GHSA-hmw2-7cc7-3qxx
fix available via `npm audit fix`
node_modules/form-data

js-yaml  <=4.1.1
Severity: moderate
JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases - https://github.com/advisories/GHSA-h67p-54hq-rp68
fix available via `npm audit fix --force`
Will install jest-watch-typeahead@0.5.0, which is a breaking change
node_modules/@istanbuljs/load-nyc-config/node_modules/js-yaml
  @istanbuljs/load-nyc-config  *
  Depends on vulnerable versions of js-yaml
  node_modules/@istanbuljs/load-nyc-config
    babel-plugin-istanbul  >=6.0.0-beta.0
    Depends on vulnerable versions of @istanbuljs/load-nyc-config
    node_modules/babel-plugin-istanbul
      @jest/transform  >=25.1.0
      Depends on vulnerable versions of babel-plugin-istanbul
      node_modules/@jest/transform
        @jest/core  >=25.1.0
        Depends on vulnerable versions of @jest/reporters
        Depends on vulnerable versions of @jest/transform
        Depends on vulnerable versions of jest-config
        Depends on vulnerable versions of jest-resolve-dependencies
        Depends on vulnerable versions of jest-runner
        Depends on vulnerable versions of jest-runtime
        Depends on vulnerable versions of jest-snapshot
        node_modules/@jest/core
          jest  >=25.1.0
          Depends on vulnerable versions of @jest/core
          Depends on vulnerable versions of jest-cli
          node_modules/jest
            jest-watch-typeahead  >=0.6.0
            Depends on vulnerable versions of jest
            node_modules/jest-watch-typeahead
          jest-cli  >=25.1.0
          Depends on vulnerable versions of @jest/core
          Depends on vulnerable versions of jest-config
          node_modules/jest-cli
        @jest/reporters  >=25.1.0
        Depends on vulnerable versions of @jest/transform
        node_modules/@jest/reporters
        jest-runner  >=25.1.0
        Depends on vulnerable versions of @jest/transform
        Depends on vulnerable versions of jest-runtime
        node_modules/jest-runner
          jest-config  >=25.1.0
          Depends on vulnerable versions of babel-jest
          Depends on vulnerable versions of jest-circus
          Depends on vulnerable versions of jest-runner
          node_modules/jest-config
        jest-runtime  >=25.1.0
        Depends on vulnerable versions of @jest/globals
        Depends on vulnerable versions of @jest/transform
        Depends on vulnerable versions of jest-snapshot
        node_modules/jest-runtime
          jest-circus  >=25.2.4
          Depends on vulnerable versions of @jest/expect
          Depends on vulnerable versions of jest-runtime
          Depends on vulnerable versions of jest-snapshot
          node_modules/jest-circus
        jest-snapshot  >=27.0.0-next.0
        Depends on vulnerable versions of @jest/transform
        node_modules/jest-snapshot
          @jest/expect  *
          Depends on vulnerable versions of jest-snapshot
          node_modules/@jest/expect
            @jest/globals  >=28.0.0-alpha.0
            Depends on vulnerable versions of @jest/expect
            node_modules/@jest/globals
          jest-resolve-dependencies  >=27.0.0-next.0
          Depends on vulnerable versions of jest-snapshot
          node_modules/jest-resolve-dependencies
      babel-jest  >=25.1.0
      Depends on vulnerable versions of @jest/transform
      Depends on vulnerable versions of babel-plugin-istanbul
      node_modules/babel-jest

19 vulnerabilities (18 moderate, 1 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

@github-actions

Copy link
Copy Markdown
Contributor
Overall Project 79.81% -0.74%
Files changed 26.25%

File Coverage
GetCrewByServiceId.kt 100% 🍏
GetAgentsCrewByMissionId.kt 100% 🍏
MissionCrew.kt 76.26% -9.34%
JPAMissionCrewRepository.kt 65.97% -8.33%
MissionCrewModel.kt 65.46% -9.79%
MissionCrewEntity.kt 58.1% -17.39%
ExportMissionPatrolSingle.kt 1.05% -2.24%
MissionCrewAbsenceModel.kt 0%
MissionCrewAbsenceEntity.kt 0%
MissionCrewAbsence.kt 0%
AddOrUpdateMissionCrew.kt 0% -45.45%

@github-actions

Copy link
Copy Markdown
Contributor
Overall Project 79.81% -0.74%
Files changed 26.25%

File Coverage
GetCrewByServiceId.kt 100% 🍏
GetAgentsCrewByMissionId.kt 100% 🍏
MissionCrew.kt 76.26% -9.34%
JPAMissionCrewRepository.kt 65.97% -8.33%
MissionCrewModel.kt 65.46% -9.79%
MissionCrewEntity.kt 58.1% -17.39%
ExportMissionPatrolSingle.kt 1.05% -2.24%
MissionCrewAbsenceModel.kt 0%
MissionCrewAbsenceEntity.kt 0%
MissionCrewAbsence.kt 0%
AddOrUpdateMissionCrew.kt 0% -45.45%

@github-actions

Copy link
Copy Markdown
Contributor
# npm audit report

js-yaml  <=4.1.1
Severity: moderate
JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases - https://github.com/advisories/GHSA-h67p-54hq-rp68
fix available via `npm audit fix --force`
Will install jest-watch-typeahead@0.5.0, which is a breaking change
node_modules/@istanbuljs/load-nyc-config/node_modules/js-yaml
  @istanbuljs/load-nyc-config  *
  Depends on vulnerable versions of js-yaml
  node_modules/@istanbuljs/load-nyc-config
    babel-plugin-istanbul  >=6.0.0-beta.0
    Depends on vulnerable versions of @istanbuljs/load-nyc-config
    node_modules/babel-plugin-istanbul
      @jest/transform  >=25.1.0
      Depends on vulnerable versions of babel-plugin-istanbul
      node_modules/@jest/transform
        @jest/core  >=25.1.0
        Depends on vulnerable versions of @jest/reporters
        Depends on vulnerable versions of @jest/transform
        Depends on vulnerable versions of jest-config
        Depends on vulnerable versions of jest-resolve-dependencies
        Depends on vulnerable versions of jest-runner
        Depends on vulnerable versions of jest-runtime
        Depends on vulnerable versions of jest-snapshot
        node_modules/@jest/core
          jest  >=25.1.0
          Depends on vulnerable versions of @jest/core
          Depends on vulnerable versions of jest-cli
          node_modules/jest
            jest-watch-typeahead  >=0.6.0
            Depends on vulnerable versions of jest
            node_modules/jest-watch-typeahead
          jest-cli  >=25.1.0
          Depends on vulnerable versions of @jest/core
          Depends on vulnerable versions of jest-config
          node_modules/jest-cli
        @jest/reporters  >=25.1.0
        Depends on vulnerable versions of @jest/transform
        node_modules/@jest/reporters
        jest-runner  >=25.1.0
        Depends on vulnerable versions of @jest/transform
        Depends on vulnerable versions of jest-runtime
        node_modules/jest-runner
          jest-config  >=25.1.0
          Depends on vulnerable versions of babel-jest
          Depends on vulnerable versions of jest-circus
          Depends on vulnerable versions of jest-runner
          node_modules/jest-config
        jest-runtime  >=25.1.0
        Depends on vulnerable versions of @jest/globals
        Depends on vulnerable versions of @jest/transform
        Depends on vulnerable versions of jest-snapshot
        node_modules/jest-runtime
          jest-circus  >=25.2.4
          Depends on vulnerable versions of @jest/expect
          Depends on vulnerable versions of jest-runtime
          Depends on vulnerable versions of jest-snapshot
          node_modules/jest-circus
        jest-snapshot  >=27.0.0-next.0
        Depends on vulnerable versions of @jest/transform
        node_modules/jest-snapshot
          @jest/expect  *
          Depends on vulnerable versions of jest-snapshot
          node_modules/@jest/expect
            @jest/globals  >=28.0.0-alpha.0
            Depends on vulnerable versions of @jest/expect
            node_modules/@jest/globals
          jest-resolve-dependencies  >=27.0.0-next.0
          Depends on vulnerable versions of jest-snapshot
          node_modules/jest-resolve-dependencies
      babel-jest  >=25.1.0
      Depends on vulnerable versions of @jest/transform
      Depends on vulnerable versions of babel-plugin-istanbul
      node_modules/babel-jest

undici  7.0.0 - 7.27.2
Severity: high
undici vulnerable to TLS certificate validation bypass via dropped requestTls in SOCKS5 ProxyAgent - https://github.com/advisories/GHSA-vmh5-mc38-953g
undici vulnerable to cross-user information disclosure via shared cache whitespace bypass - https://github.com/advisories/GHSA-pr7r-676h-xcf6
undici vulnerable to HTTP header injection via Set-Cookie percent-decoding - https://github.com/advisories/GHSA-p88m-4jfj-68fv
undici WebSocket client vulnerable to denial of service via fragment count bypass - https://github.com/advisories/GHSA-vxpw-j846-p89q
undici vulnerable to cross-origin request routing via SOCKS5 proxy pool reuse - https://github.com/advisories/GHSA-hm92-r4w5-c3mj
undici vulnerable to HTTP response queue poisoning via keep-alive socket reuse - https://github.com/advisories/GHSA-35p6-xmwp-9g52
undici vulnerable to Set-Cookie SameSite attribute downgrade via permissive substring matching - https://github.com/advisories/GHSA-g8m3-5g58-fq7m
fix available via `npm audit fix`
node_modules/undici

19 vulnerabilities (18 moderate, 1 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

@github-actions

Copy link
Copy Markdown
Contributor
Overall Project 79.81% -0.74%
Files changed 26.25%

File Coverage
GetCrewByServiceId.kt 100% 🍏
GetAgentsCrewByMissionId.kt 100% 🍏
MissionCrew.kt 76.26% -9.34%
JPAMissionCrewRepository.kt 65.97% -8.33%
MissionCrewModel.kt 65.46% -9.79%
MissionCrewEntity.kt 58.1% -17.39%
ExportMissionPatrolSingle.kt 1.05% -2.24%
MissionCrewAbsenceModel.kt 0%
MissionCrewAbsenceEntity.kt 0%
MissionCrewAbsence.kt 0%
AddOrUpdateMissionCrew.kt 0% -45.45%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants