Skip to content

[Bug] matches expression does not correctly handle non-object values #732

Description

@Luna-Klatzer

Is there an existing issue for this?

  • I have searched the existing issues

I am following the documentation's guide

  • I have read the documentation

This issue exists in the latest version

  • I am using the latest version

Current Behavior

Using the matches expression, a value is compared to a given interface, which can either result in true or false. However, using any value other than an object causes the expression to fail or return incorrect true states, due to the function being incorrectly implemented.

Expected Behavior

The matches expression should return false for those cases.

Steps To Reproduce

  • Write an interface with any number of members (may be none)
  • Use the matches expression with any primitive value, e.g.: 1 matches Xax

Environment

  • Kipper: 0.13.0-alpha.2
  • Environment: Firefox Nightly
  • Operating System: Arch Linux

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugBug or issue in the language or API

Type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions