Fix for "Null check opeator used on null value" exception.#37
Open
sheppe wants to merge 1 commit intokechankrisna:masterfrom
Open
Fix for "Null check opeator used on null value" exception.#37sheppe wants to merge 1 commit intokechankrisna:masterfrom
sheppe wants to merge 1 commit intokechankrisna:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I encountered this exception when dynamically building data table headers and the data list. The headers were defined using the bare minimum text and value properties, and this error cropped up when assigning them to the table. The .expanded property was a null value and threw an exception.