More detailed error messages #30
Merged
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
|
👍 |
Remi-Gau
added a commit
that referenced
this pull request
Feb 4, 2022
[pre-commit.ci] pre-commit autoupdate
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.
Here's a suggestion for more detailed error messages. This mostly involves including the actual problematic values in error messages, including a specific reason/underlying error message for a failure, or telling which BIDS file/dir it was trying to process when the error occurred. This will make it easier for users to diagnose errors when using BIDS-MATLAB.
It also switches to using the
catch <err>syntax where appropriate. This syntax is supported by all Matlab and Octave versions indicated in #22, and is more concise than callinglasterror().