Fix resolving coded types while typing in ETB STUD-69826 #319
Conversation
This file contains 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
AlvinStanescu
approved these changes
Apr 29, 2024
aoltean16
requested changes
May 9, 2024
aoltean16
force-pushed
the
fix/generic_types_with_type_from_other_assemblies_not_resolved
branch
from
d2e9a9d
to
f721cd6
Compare
aoltean16
approved these changes
May 15, 2024
aoltean16
changed the title
aoltean16
deleted the
fix/generic_types_with_type_from_other_assemblies_not_resolved
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 resolves the issue where typing in an expressionTextbox expecting a return type of a type with a generic argument type comes from an assembly that is in another ALC, than his parent.
E.g. List as a returnType in an expressionTextbox, it would fail, as reflection cannot resolve at-once a type from string, if atleast one of its children come from another ALC, so we resolve type-by-type and compose the resulting type in the end.
Jira
https://uipath.atlassian.net/browse/STUD-69826