Fix Event core object #3232
Merged
Fix Event core object #3232
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
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.
Context
We have a few objects that are not standard objects which means they are not part of the metadata tables (such as user, workspace, refreshToken, etc). However, those objects are defined in the code in their own resolvers and exposed in the same graphql schema shared with standard and custom objects.
Implementation
ex: "Event" custom object can be created which breaks the generation of the graphql schema because we already defined a createEvent in our analytic resolver.
Because of that, we have introduced a check in the createObject endpoint to reject some names. This PR adds some missing objects that have their own resolvers and could conflict with custom objects