not matcher gives undefined error

[PaulL1]

I have a page on which I'm running a test.

expect(element(by.id("label_email")).getText()).toEqual("Email:");

works fine. The negative of that does not work:

expect(element(by.id("label_email")).getText()).not.toEqual("Email:");

Is this expected behaviour, or a defect? I can get around this by using an ugly matcher:

expect(element(by.id("label_email")).getText().toMatch(/^(?!Email:).*$/);

but that isn't quite so elegant.

Background:
What I'm looking to do is to validate my i18n, using angular_translate. My translation keys all start with a known value depending on the item - so they are BTN_xxxx, or LABEL_xxxx. In verifying the translations I therefore would like to have something like:

expect(element(by.id("label_email")).getText().not.toMatch(/LABEL/);

The move convoluted matcher I described above works, but is a bit obscure to the casual reader.

[PaulL1]

I see when looking through the code that this looks like it was fixed under issue #139, with commit 137d804. On that basis, I'm closing assuming it's fixed, and will wait for the next release to deliver it.

[juliemr]

Yup! Hoping to get 0.13.0 out this week with the fix.