Skip to content
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

Merged
merged 34 commits into from
Jun 25, 2024
Merged

Rhino interfaces for testing #3523

merged 34 commits into from
Jun 25, 2024

Conversation

adamhathcock
Copy link
Member

@adamhathcock adamhathcock changed the base branch from main to dui3/alpha June 18, 2024 12:39
@adamhathcock adamhathcock changed the title Rhino interfaces Rhino interfaces for testing Jun 20, 2024
@adamhathcock adamhathcock marked this pull request as ready for review June 20, 2024 11:00
@adamhathcock
Copy link
Member Author

IProxyMapper moved to this usage while reusing source gen version that is host app specific

@adamhathcock adamhathcock enabled auto-merge (squash) June 21, 2024 09:42
@@ -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()}");
Copy link
Member

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?

Copy link
Member Author

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

Copy link
Member

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.

@adamhathcock adamhathcock merged commit 207753c into dui3/alpha Jun 25, 2024
33 checks passed
@adamhathcock adamhathcock deleted the rhino-interfaces branch June 25, 2024 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants