-
Notifications
You must be signed in to change notification settings - Fork 91
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
ETQ dev, je souhaite que les méthodes de manipulation des répétitions soient consolidées et tiennent compte des projections #10715
Conversation
PR Summary
This PR endeavors to enhance how the application handles champs and their various contexts, states, and values. Improvements in user tracking also provide greater insight and traceability into champ updates. |
f2cfcbd
to
7ec8b25
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #10715 +/- ##
=======================================
Coverage 84.68% 84.69%
=======================================
Files 1132 1130 -2
Lines 25098 25064 -34
Branches 4703 4701 -2
=======================================
- Hits 21255 21228 -27
+ Misses 3843 3836 -7 ☔ View full report in Codecov by Sentry. |
7ec8b25
to
a167bd4
Compare
7900fd4
to
bb5b82a
Compare
2a5a9ca
to
84590b9
Compare
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.
1ere passe, c'est canon !
Voici un petit patch pour virer du code mort qui utilisait le DataFixer::DossierChampsMissing
0001-clean-deadcode-remove-deadcode.patch
added_champs | ||
def add_row(updated_by:) | ||
# TODO: clean this up when parent_id is deprecated | ||
row_id, added_champs = dossier.repetition_add_row(type_de_champ, updated_by:) |
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.
Spontannément j'aurais inliné la methode dossier.repetition_add_row(type_de_champ, updated_by:)
ici (seul appel de cette methode est ici). J'ai l'impression que c'est une indirection de trop, ça me perturbe. T'as voulu collocaliser la gestion des repetitions dans le concern ?
dossier.champs.where(row_id:).destroy_all | ||
dossier.champs.reload | ||
def remove_row(row_id, updated_by:) | ||
dossier.repetition_remove_row(type_de_champ, row_id, updated_by:) |
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.
Spontannément j'aurais inliné la methode dossier.repetition_remove_row(type_de_champ, row_id, updated_by:)
ici (seul appel de cette methode est ici). J'ai l'impression que c'est une indirection de trop, ça me perturbe. T'as voulu collocaliser la gestion des repetitions dans le concern ?
84590b9
to
a8e605f
Compare
2a80091
No description provided.