-
Notifications
You must be signed in to change notification settings - Fork 636
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
Make IntegerSlider the only AKA for migration #11360
Conversation
There were two classes that were declaring an 'AlsoKnownAs' attribute for 'DSCoreNodesUI.Input.IntegerSlider' in 'CoreNodeModels.Input': 'IntegerSlider' and 'IntegerSlider64Bit'. Since the latter obsoletes the former, it should be the only one declaring an 'AlsoKnownAs' attribute. Note that currently both are trying to be registered, which results in only one of them being registered but not really making any guarantees of which one it is. This also generate an exception catched internally but showed in the console.
@mmisol could you share a reproducible case? I suspect you see an exception when you try to open a legacy graph using the |
After discussing with @aparajit-pratap and seeing the migration from XML to |
There were two classes that were declaring an 'AlsoKnownAs' attribute for 'DSCoreNodesUI.Input.IntegerSlider' in 'CoreNodeModels.Input': 'IntegerSlider' and 'IntegerSlider64Bit'. While the latter obsoletes the former, it is not possible to migrate to it from XML, so only 'IntegerSlider' should continue declaring an 'AlsoKnownAs' attribute. Note that currently both classes are trying to be registered, which results in only one of them being registered but not really making any guarantees of which one it is. This also generates an exception catched internally but shown in the console.
* Dock and Undock view extension with Dynamic extension ID as edge case (#11394) * Initial Commit with settings null check * Add unit test * Add view extension loading warning * Update message * Initial Commit (#11366) * Do not aggregate node execution analytics anymore (#11356) * Do not aggregate node execution analytics anymore * Update to use new event combo * Update Comments * Make IntegerSlider the only AKA for migration (#11360) There were two classes that were declaring an 'AlsoKnownAs' attribute for 'DSCoreNodesUI.Input.IntegerSlider' in 'CoreNodeModels.Input': 'IntegerSlider' and 'IntegerSlider64Bit'. While the latter obsoletes the former, it is not possible to migrate to it from XML, so only 'IntegerSlider' should continue declaring an 'AlsoKnownAs' attribute. Note that currently both classes are trying to be registered, which results in only one of them being registered but not really making any guarantees of which one it is. This also generates an exception catched internally but shown in the console. * Revised icons for AnyTrue and AnyFalse nodes (#11361) * Implement ToString for DS Dictionary (#11358) This is done to provide meaningful output when a dictionary is provided to nodes like 'String from Array' and 'String from Object'. These nodes call built-in DS functions that end up calling ToString on the dictionary, which until now used the default implementation inherited from Object which just returned the class name. Co-authored-by: Martin Misol Monzo <[email protected]> Co-authored-by: Laurence Elsdon <[email protected]>
Purpose
There were two classes that were declaring an 'AlsoKnownAs' attribute
for 'DSCoreNodesUI.Input.IntegerSlider' in 'CoreNodeModels.Input':
'IntegerSlider' and 'IntegerSlider64Bit'. While the latter obsoletes
the former, it is not possible to migrate to it from XML, so only
'IntegerSlider' should continue declaring an 'AlsoKnownAs' attribute.
Note that currently both classes are trying to be registered, which
results in only one of them being registered but not really making any
guarantees of which one it is. This also generates an exception catched
internally but shown in the console.
Declarations
Check these if you believe they are true
*.resx
files