Skip to content

Remove leading / from product-menu-sprite #263

Remove leading / from product-menu-sprite

Remove leading / from product-menu-sprite #263

Triggered via push September 4, 2023 10:29
Status Success
Total duration 6m 24s
Artifacts

CD.yml

on: push
Deploy interflux.com (Frankfurt)
1m 0s
Deploy interflux.com (Frankfurt)
Deploy interflux.de (Frankfurt)
55s
Deploy interflux.de (Frankfurt)
Deploy interflux.es (Madrid)
1m 14s
Deploy interflux.es (Madrid)
Deploy interflux.fr (Paris)
1m 12s
Deploy interflux.fr (Paris)
Deploy interflux.mx (Mexico)
1m 9s
Deploy interflux.mx (Mexico)
Deploy interflux.cn.com (Osaka)
1m 18s
Deploy interflux.cn.com (Osaka)
Fit to window
Zoom out
Zoom in

Annotations

17 warnings
Test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test: app/templates/head.hbs#L21
Ambiguous path 'cdn' is not allowed. Use '@cdn' if it is a named argument or 'this.cdn' if it is a property on 'this'. If it is a helper or component that has no arguments, you must either convert it to an angle bracket invocation or manually add it to the 'no-implicit-this' rule configuration, e.g. 'no-implicit-this': { allow: ['cdn'] }.
Test: app/pods/company/template.hbs#L95
Ambiguous path 'cdn' is not allowed. Use '@cdn' if it is a named argument or 'this.cdn' if it is a property on 'this'. If it is a helper or component that has no arguments, you must either convert it to an angle bracket invocation or manually add it to the 'no-implicit-this' rule configuration, e.g. 'no-implicit-this': { allow: ['cdn'] }.
Test: app/pods/components/checkbox/template.hbs#L1
<div> has a role of checkbox, it cannot have semantic descendants like <Svg::Check>
Test: app/pods/components/contact-page/template.hbs#L28
Ambiguous path 'cdn' is not allowed. Use '@cdn' if it is a named argument or 'this.cdn' if it is a property on 'this'. If it is a helper or component that has no arguments, you must either convert it to an angle bracket invocation or manually add it to the 'no-implicit-this' rule configuration, e.g. 'no-implicit-this': { allow: ['cdn'] }.
Test: app/pods/components/contact-page/template.hbs#L57
Ambiguous path 'cdn' is not allowed. Use '@cdn' if it is a named argument or 'this.cdn' if it is a property on 'this'. If it is a helper or component that has no arguments, you must either convert it to an angle bracket invocation or manually add it to the 'no-implicit-this' rule configuration, e.g. 'no-implicit-this': { allow: ['cdn'] }.
Test: app/pods/components/footer/template.hbs#L6
Ambiguous path 'cdn' is not allowed. Use '@cdn' if it is a named argument or 'this.cdn' if it is a property on 'this'. If it is a helper or component that has no arguments, you must either convert it to an angle bracket invocation or manually add it to the 'no-implicit-this' rule configuration, e.g. 'no-implicit-this': { allow: ['cdn'] }.
Test: app/pods/components/footer/template.hbs#L24
Ambiguous path 'cdn' is not allowed. Use '@cdn' if it is a named argument or 'this.cdn' if it is a property on 'this'. If it is a helper or component that has no arguments, you must either convert it to an angle bracket invocation or manually add it to the 'no-implicit-this' rule configuration, e.g. 'no-implicit-this': { allow: ['cdn'] }.
Test: app/pods/components/footer/template.hbs#L34
Ambiguous path 'cdn' is not allowed. Use '@cdn' if it is a named argument or 'this.cdn' if it is a property on 'this'. If it is a helper or component that has no arguments, you must either convert it to an angle bracket invocation or manually add it to the 'no-implicit-this' rule configuration, e.g. 'no-implicit-this': { allow: ['cdn'] }.
Test: app/pods/components/footer/template.hbs#L103
Use of <nobr> detected. Do not use deprecated elements.
Test: app/pods/components/home-page/template.hbs#L24
Potential path in attribute string detected. Did you mean {{@640x1200.jpg,@640x1200.webp}}?
Deploy interflux.com (Frankfurt)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy interflux.de (Frankfurt)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy interflux.mx (Mexico)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy interflux.fr (Paris)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy interflux.es (Madrid)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy interflux.cn.com (Osaka)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/