Migrate created_at related triggers to the API #3294
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
cesarvarela
had a problem deploying
to
staging
GitHub Actions
Failure
|
Thanks, I also exposed the field in the schema. And yes, we'll have to track where insertions happen and ensure the |
|
@cesarvarela I think the same issue is happening for |
cesarvarela
had a problem deploying
to
staging
GitHub Actions
Failure
clari182
approved these changes
Dec 24, 2024
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.
The
created_atfield should be added to every graphql type where it applies, and some tests added, but I think that's outside the scope of this PR which is just migrating it so we can get rid of Atlas.