Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Suppression du warning de division par 0 #164
Suppression du warning de division par 0 #164
Changes from 2 commits
852efb3
65c3350
0ddc145
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revue naïve: avec cette modification, le taux d'effort vaut l'infini si les ressources sont nulles. Est-ce que c'est bien ce qu'on veut ? Est-ce que tu pourrais ajouter un scénario de test pour appliquer ce cas ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
De mémoire, c'est déjà visible en mode : Tu lances les tests sans le fix et tu les relances avec le fix @Shamzic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ce que je veux dire, c'est que si
paris_taux_effort
vaut l'infini, alorsparis_condition_taux_effort
vauttrue
et je suis pas si sûr que ça soit forcément ce résultat qui est attendu, mais peut-être que c'est ok après toutThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pour moi, si tu n'as pas de revenu ton taux d'effort est infini si tu dois par exemple payer un loyer.
Si tu as un peu de revenu mathématiquement on peux définir ce taux d'effort comme pourrait le faire une banque dans le cas d'une demande de prêt. Donc pour moi c'est ok. Sauf si tu as une idée pour une autre implémentation. De mon côté, je te propose de partir dans cette direction et itérer. Cela permettra de supprimer l'erreur dans les logs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, du coup je mets en image le test qui vérifie la modification actuelle dans le fichier tests/unittests/paris.yaml :