Skip to content

This fixes a Bug in the ValueResolver #2531

Merged
bbakerman merged 2 commits intomasterfrom
fixes-to-object-value-printing
Sep 2, 2021
Merged

This fixes a Bug in the ValueResolver #2531
bbakerman merged 2 commits intomasterfrom
fixes-to-object-value-printing

Conversation

@bbakerman
Copy link
Copy Markdown
Member

This fixes a Bug in the ValueResolver when called from the SchemaPrinter such that object values had null names

It also adds some handy Value.of methods to make AST VALUE literals easier to use

@bbakerman bbakerman added this to the 18.0 milestone Sep 1, 2021

}

@Ignore("ObjectValue.isEqualTo is broken - this test currently makes no sense")
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I had to Ignore this test because its broken - ObjectValue.isEqualTo is not implemented properly

That I dont think the code itself worths either because its an empty ObjectValue anyway.

But since this is not part of this PR - I am ignoring it to allow progress over perfection

(It will assert with the new asserts I put in - hence it will break but not for good reasons)

InputValueDefinition.newInputValueDefinition().build() | 'visitInputValueDefinition'
InputValueDefinition.newInputValueDefinition().build() | 'visitInputValueDefinition'
new ObjectField("", null) | 'visitObjectField'
new ObjectField("a", IntValue.of(1)) | 'visitObjectField'
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

No longer valid

@bbakerman bbakerman merged commit 8530366 into master Sep 2, 2021
@bbakerman bbakerman modified the milestones: 18.0, 17.3 Sep 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants