You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the NanoporeParser returns the everit ValidationException if the provided filetree doesn't follow the predefined schema.
This leads to the Issue that the applications using the NanoporeParser have to include the everit package as a dependency to interpret the exception.
Additionally, it returns different uncatched exceptions(IOException/ParserException/FileNotFoundException) dependent on why the parsing fails.
Describe the solution you'd like
Replace the ValidationException with the custom DatasetValidationException akin to the BioionformaticAnalysisParser and the MaxQuantParser.
The different Exceptions which could be generated during the parsing of a filetree, should be catched akin to the BioionformaticAnalysisParser and the MaxQuantParser and a custom DataParserException should be thrown for easier debugging.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently the
NanoporeParser
returns the everitValidationException
if the provided filetree doesn't follow the predefined schema.This leads to the Issue that the applications using the
NanoporeParser
have to include the everit package as a dependency to interpret the exception.Additionally, it returns different uncatched exceptions(
IOException
/ParserException
/FileNotFoundException
) dependent on why the parsing fails.Describe the solution you'd like
Replace the
ValidationException
with the customDatasetValidationException
akin to theBioionformaticAnalysisParser
and theMaxQuantParser
.The different Exceptions which could be generated during the parsing of a filetree, should be catched akin to the
BioionformaticAnalysisParser
and theMaxQuantParser
and a customDataParserException
should be thrown for easier debugging.The text was updated successfully, but these errors were encountered: