Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide validation warning under env variable #4843 #5085

Conversation

angrykoala
Copy link
Member

To avoid verbose output on valid use cases when using the OGM, the warning on object fields without a resolver is now shown under the DEBUG env variable

Copy link

changeset-bot bot commented May 7, 2024

🦋 Changeset detected

Latest commit: c82f7b8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@neo4j/graphql Patch
@neo4j/graphql-ogm Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@@ -44,48 +43,45 @@ describe("WarnObjectFieldsWithoutResolver", () => {
afterEach(() => {
warn.mockReset();
});
describe("Does not show warning", () => {
test("Error on object field array without resolver throw warning in debug", () => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
test("Error on object field array without resolver throw warning in debug", () => {
test("Error on object field array without resolver throw warning in debug", () => {

@angrykoala angrykoala merged commit 2a57cf3 into dev May 7, 2024
81 checks passed
@angrykoala angrykoala deleted the 4843-objects-fully-defined-by-custom-queries-should-not-throw-warnings-about-unresolved-fields branch May 7, 2024 12:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Pull requests
Development

Successfully merging this pull request may close these issues.

Objects fully defined by custom queries should not throw warnings about unresolved fields.
3 participants