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.

Sign up for GitHub

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

Jump to bottom

Operator '<>' cannot be applied to types 'object' and 'string' #1387

Closed
TwitchBronBron opened this issue Jan 3, 2025 · 0 comments
Closed

Operator '<>' cannot be applied to types 'object' and 'string' #1387

TwitchBronBron opened this issue Jan 3, 2025 · 0 comments
Milestone
v1.0.0

Comments

@TwitchBronBron
Copy link
Member

This error below should not be an error, and any object types should probably be treated the same as dynamic.

Image

Justification: The object type is almost the same as dynamic, except it rejects the uninitialized type when called.

Image
@TwitchBronBron TwitchBronBron added this to the v1.0.0 milestone Jan 3, 2025
markwpearce added a commit that referenced this issue Jan 14, 2025
@markwpearce
Binary and Unary operators handle ObjectType - issue #1387
152da3b
markwpearce added a commit that referenced this issue Jan 14, 2025
@markwpearce
Fixes How BinaryOperators work on Unions (#1400)
7fb92ff 
* Binary operators on Unions work better now

* Used same logic on unary operators as well

* Updated test to check result type of complex binrary operation

* Binary and Unary operators handle ObjectType - issue #1387
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v1.0.0
Development

No branches or pull requests
2 participants
@markwpearce @TwitchBronBron