Another Null Pointer #150
Merged
Another Null Pointer #150
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
internal reference existed within a external referenced spec. This currently leaves the internal reference unprocessed.
internal reference existed within a external referenced spec. This currently leaves the internal reference unprocessed.
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.
Looks like there was another issue in my commit - if the spec being processed had an internal ref it ended up generating a null pointer exception when processRefToExternalDefinition() was recursively called as the Model was null when pulled from the cache.
Added a check to make sure it's an external ref before processing. This does lead to a situation in which some definitions are left unprocessed