Introduced DriverException and fixed constructors of specific driver exceptions#993
Merged
Conversation
dbeuchler
force-pushed
the
fix/driver-exceptions
branch
from
d19ce0e to
e2d1d5b
Compare
andreniggemann
approved these changes
Jan 13, 2026
1nf0rmagician
approved these changes
Jan 13, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
We could think about marking MarkingException, MarkingFileException and MoveAxesException as obsolete in 10.1 because they do not define additional properties and therefore they are useless. A classic case of releasing too quickly and not testing in the application. Remember in MORYX 12.