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

[BO][Staging] Des signalements avec qualifications sont non accessibles #2143

Merged
merged 1 commit into from
Jan 24, 2024

Conversation

sfinx13
Copy link
Collaborator

@sfinx13 sfinx13 commented Jan 24, 2024

Ticket

#2142

Description

L'une des dernières migrations applique null comme valeur par défaut pour desordre_precision_ids, alors que l'attribut de la classe est de type tableau uniquement ce qui provoque l'erreur 500 après que l'objet signalementQualification soit hydraté.

Autoriser donc que l'attribut de la classe puisse accepter null comme valeur.

Changements apportés

  • Mise à jour du typage desordrePrecisionIds

Pré-requis

Tests

  • Mettre à jour un signalement avec null pour signalementQualification::desordre_precision_ids avant de récupérer la PR et constater l'erreur
  • Récupérer la branche et vérifier que la fiche s'affiche.

Copy link

sonarcloud bot commented Jan 24, 2024

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

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

See analysis details on SonarCloud

@sfinx13 sfinx13 changed the title [BO][Staging] Des signalements sont non accessibles [BO][Staging] Des signalements avec qualifications sont non accessibles Jan 24, 2024
Copy link
Collaborator

@emilschn emilschn left a comment

Choose a reason for hiding this comment

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

OK relecture et test !

@emilschn emilschn merged commit 979ee9a into develop Jan 24, 2024
3 checks passed
@sfinx13 sfinx13 deleted the bugfix/2142-signalement-error-500 branch February 13, 2024 21:04
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.

None yet

2 participants