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.
Notes:
Everything here seems to work, the main question I have is when to populate
registered_at
- I see two options:Until we have an answer to this, I'm using a very direct approach - getting the db to populate
registered_at
when the row is created. I don't love this approach, because it isn't exposed in the code/editable later - but something like anafter_create
hook feels very redundant (given that we havecreated_at
) with my current understanding, so I just went with something simple while we discuss the implementation.TODO
registered_at
when reg is createdregistered_at
in the frontend