Yuri Ratanov

I think it should be added as a fix for both v3.28 and v4. Even if this code will be dropped completely, at least it will allow users to upgrade....

closed in favour of #8154

@juanazam But it will break chaining, isn't it?

@juanazam not sure what you mean by "properly". I tried as you showed in your example, and it doesn't wait.

@juanazam OK, so here what helped: ```js import { getExecutionContext } from 'ember-cli-page-object/-private/execution_context'; export function powerSelect(selector) { return { isDescriptor: true, get(_) { return function(text) { let executionContext = getExecutionContext(this);...

can I help with this?

@ro0gr what if under the hood of `assert.po` we just do smth like this ```js QUnit.assert.po(pageObject) { return this.dom(pageObject.element); } ```

@ro0gr yep, I think you are right. Can I be any help with https://github.com/ro0gr/ember-qunit-page-object?

@NullVoxPopuli @ro0gr I've created a small addon for it https://github.com/yratanov/ember-page-object-asserts . It's very simple, my main goal was to make errors more descriptive. API has something in common with qunit-dom....

made few improvements to [the addon](https://github.com/yratanov/ember-page-object-asserts), now you can do this: ```js const page = create({ link: { scope: 'a', href: attribute('href'), isHighlighted: hasClass('highlighted'), } }); assert.po(page.link).href('google.com'); assert.po(page.link).isHighlighted(); ``` Directly...