feat(Besoins): mettre à jour automatiquement la date de transaction #1122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SebastienReuiller
approved these changes
Mar 8, 2024
| https://stackoverflow.com/a/23363123 | ||
| """ | ||
| super().__init__(*args, **kwargs) | ||
| for field_name in self.TRACK_UPDATE_FIELDS: |
There was a problem hiding this comment.
Je n'avais pas vu cette astuce, très sympa !
There was a problem hiding this comment.
Yes, après je me dis que ça doit être factorisable dans une classe + héritage ? À noter dans la refactoring-to-do-list ^^
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Quoi ?
Suite de #1116
Dès que le champ
siae_transactionedchange, on met à joursiae_transactioned_last_updatedComment ?
Grâce à un mécanisme similaire au modèle
Siae, avecTRACK_UPDATE_FIELDSsave(), pas des bulkupdate()