fix: graphql server metaschemas #554
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
Add debug logs for API resolution, auth, and startup config. Logs only emitted when NODE_ENV=development. Replace console.error with proper Logger calls.
yyyyaaa
changed the title
Change default metaSchemas from collections_public, meta_public to services_public, metaschema_public, metaschema_modules_public to fix NO_VALID_SCHEMAS error.
yyyyaaa
force-pushed
the
fix/graphql-server-metaschemas
branch
from
3eb128f to
b8290a4
Compare
yyyyaaa
changed the title
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.
There is a bug after we migrated and renamed things in constructive-db, which this PR addresses.
Also adds some useful loggings in DEV only.