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

Champs transportFee & sustainableMobilityFee de l'entity UserAdministrative ne devraient pas être nullable #367

Open
fuuuzz opened this issue Mar 22, 2023 · 0 comments
Assignees

Comments

@fuuuzz
Copy link
Contributor

fuuuzz commented Mar 22, 2023

En référence à #361 (comment)

En effet, les champs transportFee & sustainableMobilityFee sont définis de cette façon:

@Column({ type: 'integer', default: 0, nullable: true })

La valeur par défaut à 0, induit qu'elle ne pourra jamais être nulle. Il ne fait donc pas sens de spécifier le nullable: true.

Extrait de la doc: https://typeorm.io/entities#column-options

nullable: boolean - Makes column NULL or NOT NULL in the database. By default column is nullable: false.

Endroits à changer auxquels je pense:

@fuuuzz fuuuzz self-assigned this Mar 22, 2023
@florimondmanca florimondmanca changed the title Modifier champs transportFee & sustainableMobilityFee de l'entity UserAdministrative Champs transportFee & sustainableMobilityFee de l'entity UserAdministrative ne devraient pas être nullable Nov 6, 2023
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

No branches or pull requests

1 participant