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 PR standardizes the error handling in the parsing module by introducing specific error classes, ensuring all thrown errors are of the type
ParseErrorType
. This enhancement improves type safety, clarity, and consistency across the codebase.Changes Introduced
The following custom error classes have been introduced to represent specific parsing errors:
CouldNotDetermineFileTypeErro
r: Thrown when the parser cannot determine the file type.UnsupportedFileTypeError:
Thrown when an unsupported file type is encountered.UnexpectedFileContentError
: Thrown when the file content does not match the expected format.InternalParserError
: Thrown in case of an internal error during parsing.Unified Error Type
All the above error classes are grouped under a new union type,
KindOfParseError
, which provides a common structure for parsing-relatedEach error class shares a common
name
property, which is useful for error identification and handling (switch
ing).PR suggestion provided by sponsor @schickling:
@schickling can you please review?