[Refactor] Refactoring Usage of Dynamic Values in HasDraft Trait #48
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.
This pull request aims to refactor usages in the
HasDraft
trait, specifically addressing instances where column names for soft delete and timestamps were not utilizing dynamic values. Previously, static values such asCREATED_AT
,UPDATED_AT
, andDELETED_AT
were hardcoded, leading to potential issues.Changes made :
Additional Notes :