Ruslan Hrabovyi

I'd like to delegate that assertions api somewhere, but > if getPageObjectDefinition allows access to a selector (non-jquery selector) or element I think it isn't achievable via a single CSS...

I'd say, it gets inspiration from qunit-dom(`pushResult()` and `Qunit.extend()`), but it doesn't re-invent something. FWIW, I think, you can achieve `.dom` for each page object by decorating `create` from the...

@yratanov I think this is a perfect answer to a question "how to integrate", with that we don't even need to expose `element` from the page objects: ```js QUnit.assert.po(pageObject) {...

@yratanov thanks! Glad to see you are interested. As far as I remember, there were some complexity in parsing page object instance shape(props) due to a lack of `getPageObjectDefinition` those...

@NullVoxPopuli what do you think? is the snippet, suggested by @yratanov, something you are looking for?

@yratanov I like it! Since this issue seems to be a bit unrelated to a custom assertions API, left some initial feedback at your addon repo https://github.com/yratanov/ember-page-object-asserts/issues/1

just noticed the same issue for `deprecate`: ```js import { deprecate as emberDeprecate } from '@ember/application/deprecations'; // .... deprecate(message, // Here it fails with "TypeError: Ember.emberDeprecate is not a function"...

the other use case I've just faced is a need to pass [`multipleOfPrecision`](https://ajv.js.org/options.html#multipleofprecision) option. Without it AJV just isn't able to handle the `multipleOf` properly(https://github.com/ajv-validator/ajv/issues/84). I doubt if hardcoding any...

This all sounds really great! > I expect we would provide out-of-the-box behavior to produce type declarations for any templates found. Especially this one :rocket: My first impression after a...

This issue was closed unintentionally again. From glimmerjs/glimmer.js@8b95d66: > Ultimately, this commit should be able to be revertted once the upstream issue is resolved: ember-cli/ember-cli#6952.