Ember breaking updates #23
Yelinztests.yaml
on: pull_request
api-tests
34s
caluma-tests
2m 27s
caluma-lint
18s
ember-test
1m 49s
ember-build
1m 1s
commit-lint
10s
Annotations
12 errors and 10 warnings
|
api-tests
Process completed with exit code 17.
|
|
ember-build
Process completed with exit code 17.
|
|
ember-test
Do not use the `Input` component. Built-in form components use two-way binding to mutate values. Instead, refactor to use a native HTML element.
|
|
ember-test:
ember/app/ui/components/nav-bar/component.js#L28
Unexpected console statement
|
|
|
|
ember-test:
ember/tests/integration/ui/components/identity-address/component-test.js#L3
There should be at least one empty line between import groups
|
|
ember-test:
ember/tests/integration/ui/components/identity-address/component-test.js#L4
There should be at least one empty line between import groups
|
|
ember-test:
ember/tests/integration/ui/components/identity-address/component-test.js#L4
`mysagw/tests/helpers` import should occur after import of `qunit`
|
|
ember-test:
ember/tests/integration/ui/components/identity-emails/component-test.js#L3
There should be at least one empty line between import groups
|
|
ember-test:
ember/tests/integration/ui/components/identity-emails/component-test.js#L4
There should be at least one empty line between import groups
|
|
ember-test:
ember/tests/integration/ui/components/identity-emails/component-test.js#L4
`mysagw/tests/helpers` import should occur after import of `qunit`
|
|
ember-test:
ember/tests/integration/ui/components/nav-bar/component-test.js#L17
Replace `'service:intl')` with `"service:intl");`
|
|
ember-test
Do not use the `did-insert` modifier. This modifier was intended to ease migration to Octane and not for long-term side-effects. Instead, refactor to use a custom modifier. See https://github.com/ember-modifier/ember-modifier
|
|
ember-test
Do not use the `did-update` modifier. This modifier was intended to ease migration to Octane and not for long-term side-effects. Instead, refactor to use a custom modifier. See https://github.com/ember-modifier/ember-modifier
|
|
ember-test
Do not use the `did-insert` modifier. This modifier was intended to ease migration to Octane and not for long-term side-effects. Instead, refactor to use a custom modifier. See https://github.com/ember-modifier/ember-modifier
|
|
ember-test
Do not use the `did-update` modifier. This modifier was intended to ease migration to Octane and not for long-term side-effects. Instead, refactor to use a custom modifier. See https://github.com/ember-modifier/ember-modifier
|
|
ember-test
Do not use the `did-insert` modifier. This modifier was intended to ease migration to Octane and not for long-term side-effects. Instead, refactor to use a custom modifier. See https://github.com/ember-modifier/ember-modifier
|
|
ember-test
Do not use the `did-update` modifier. This modifier was intended to ease migration to Octane and not for long-term side-effects. Instead, refactor to use a custom modifier. See https://github.com/ember-modifier/ember-modifier
|
|
ember-test
Do not use the `did-insert` modifier. This modifier was intended to ease migration to Octane and not for long-term side-effects. Instead, refactor to use a custom modifier. See https://github.com/ember-modifier/ember-modifier
|
|
ember-test
Do not use the `did-update` modifier. This modifier was intended to ease migration to Octane and not for long-term side-effects. Instead, refactor to use a custom modifier. See https://github.com/ember-modifier/ember-modifier
|
|
ember-test
Do not use the `did-insert` modifier. This modifier was intended to ease migration to Octane and not for long-term side-effects. Instead, refactor to use a custom modifier. See https://github.com/ember-modifier/ember-modifier
|
|
ember-test
Do not use the `did-update` modifier. This modifier was intended to ease migration to Octane and not for long-term side-effects. Instead, refactor to use a custom modifier. See https://github.com/ember-modifier/ember-modifier
|