loadJSONObject/Array() now return null if the given file was not found #6081
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
benfry
added a commit
to benfry/processing4
that referenced
this pull request
Sep 23, 2020
Contributor
|
Thanks; this is now incorporated for 4.0 alpha 3: processing/processing4@2b19ff8 |
|
This pull request has been automatically locked. Pull requests that have been closed are automatically locked 30 days after the last comment. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
All data loading functions such as loadBytes() and loadXML() return null instead of throwing an exception when the given file was not found. On the other hand, loadJSONObject() and loadJSONArray() throws NullPointerException. This is not consistent.
This patch fixes this problem and gives the developers a consistent error handling way to other loading functions.