add support for importing createdAt #30
Merged
Conversation
This file contains hidden or 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
Member
|
Hi @dlo. Thanks for the PR. We had started a large refactor on this that got shelved. I recently picked that back up and am about to release it. While this PR is mostly out of date compared to #11 I did take the idea from here and added |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It's helpful to see when the user actually signed up, versus just when the user was imported into Clerk. This change addresses this by allowing the
createdAtvalue to be optionally provided inusers.json. This parameter is already supported by thecreateUserfunction, so all I did was add the additional parameter to the zod schema and carry it over to the function call.I've added a usage example in the sample file as well.