Allow to globally disable null-checks of LSP data structures #343
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
spoenemann
force-pushed
the
customizeNullChecks
branch
from
e201ccc
to
9ad21df
Compare
Thank you for this patch, @spoenemann! I am no sure if I ever want to change the runtime behavior with a boolean flag, but I do not have anything against this PR. |
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.
Follow-up of #305. This allows to globally disable the null-checks in applications where they cause more trouble than they actually help. See the discussion:
https://github.com/eclipse/xtext-core/pull/1060/files/853bfb6536c406f26ca53f17eef9189e649beb2e#pullrequestreview-210108691
@kittaakos @cdietrich would this change improve the situation?