Skip to content

Void return types need to always be null value#729

Merged
jonahgraham merged 1 commit into
mainfrom
jonah/fixes_721
May 9, 2023
Merged

Void return types need to always be null value#729
jonahgraham merged 1 commit into
mainfrom
jonah/fixes_721

Conversation

@jonahgraham

Copy link
Copy Markdown
Contributor

Void type in Java cannot be instantiated, therefore if a type is declared as Void the fromJson should always set that value to null.

If you want to have a generic return type that allows non-null and null results, use a type other than Void as the return type.

Fixes #721

Void type in Java cannot be instantiated, therefore if a
type is declared as Void the fromJson should always set that
value to null.

If you want to have a generic return type that allows non-null
and null results, use a type other than Void as the return type.

Fixes #721
@jonahgraham

Copy link
Copy Markdown
Contributor Author

This has recreated #728 but in the eclipse/lsp4j repo so that we can get a p2 site out of it easily.

@jonahgraham

Copy link
Copy Markdown
Contributor Author

@sebthom

sebthom commented May 5, 2023

Copy link
Copy Markdown
Contributor

I tested it with the Haxe and Dart Debug Adapters and it works fine.

@jonahgraham jonahgraham merged commit 79df5e2 into main May 9, 2023
@jonahgraham jonahgraham deleted the jonah/fixes_721 branch May 9, 2023 15:37
@jonahgraham jonahgraham added this to the 0.21.0 milestone May 17, 2023
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.

configurationDone signature incorrectly says "Void"

2 participants