prevent null reference exceptions in editor when using not-serializab… #371
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
AdamRamberg
requested changes
Oct 23, 2022
AdamRamberg
approved these changes
Oct 23, 2022
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.
this is taking only the relevant parts of PR #304. Special thanks to @IceTrooper.
I created a new PR to keep all the small refactoring changes out, which resulted in merge conflicts and much noise.
In AtomBaseReferenceDrawer > OnGUI: the diff looks like much, but I actually just wrapped the previous code in an if-else branch and I'm showing a label if the property is not serializable. the else branch is unchanged.
I suggest in the "files changed"-tab select the settings-icon and "hide whitespaces" so the indentation does not confuse the diff coloring