-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rhino interfaces for testing #3523
Conversation
IProxyMapper moved to this usage while reusing source gen version that is host app specific |
eaa0b1e
to
63d3016
Compare
DUI3-DX/Converters/Rhino/Speckle.Converters.Rhino7/ToSpeckle/Raw/BrepToSpeckleConverter.cs
Outdated
Show resolved
Hide resolved
DUI3-DX/Converters/Rhino/Speckle.Converters.Rhino7/ToSpeckle/Raw/BrepToSpeckleConverter.cs
Show resolved
Hide resolved
@@ -27,7 +27,7 @@ public Base Convert(Type type, object obj) | |||
|
|||
if (objectConverter == null) | |||
{ | |||
throw new NotSupportedException($"No conversion found for {type.Name}"); | |||
throw new NotSupportedException($"No conversion found for {type.Name} with actual type of {obj.GetType()}"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it important to know the obj type here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is for debugging purposes where the converter being asked for wasn't the type passed...this is a case for a lot of things at least in the Revit converter
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only concern with this, is this is a very common user facing error message. And it would be nice for normal users to intuitively understand that "this type of object, isn't supported by us". I wasn't sure if this starts to confound some internal implementation complexity.
Perhaps we should instead by wrapping higher up...
Not a blocker, I just expect we'll have some feedback about this change to the error message.
https://spockle.atlassian.net/browse/DUI3-319