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

InputMapping does not infer available type mappings on polymorphic operators #1290

Closed
glopesdev opened this issue Mar 17, 2023 · 0 comments · Fixed by #1291
Closed

InputMapping does not infer available type mappings on polymorphic operators #1290

glopesdev opened this issue Mar 17, 2023 · 0 comments · Fixed by #1291
Labels
bug Something isn't working

Comments

@glopesdev
Copy link
Member

glopesdev commented Mar 17, 2023

The InputMapping node is invaluable in simplifying type conversion logic by doing inference over available overloads in the successor node. Currently, this ability does not extend to polymorphic operators, which blocks integration of polymorphic types as first-class citizens in the language.

Support seems relatively simple and non-committal to implement using the ICustomTypeDescriptor interface. Since type mappings are purely based on editor inference, future-proofing is guaranteed at the language model level where types are indeed explicitly declared (i.e. if this type inference approach were to change in the future, nothing in the serialized workflow model would need to change).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant