wickes-css2 2.112.0-why-not-add.5 → 2.112.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/Readme.md +0 -4
- package/build/js/bloomreach-widget.min.js +1 -1
- package/build/js/emulation.min.js +2446 -2397
- package/build/js/page/bloomreach-widget/bloomreach-widget-tracking.js +87 -0
- package/build/js/page/bloomreach-widget/complete-your-project-widget.js +65 -0
- package/build/js/page/bloomreach-widget/why-not-add-widget.js +34 -2
- package/build/js/page/checkout-payment-details.js +10 -0
- package/build/js/page/utils/data-layer.js +9 -0
- package/package.json +1 -5
- package/src/components/address-billie.hbs +22 -18
- package/src/components/checkout-edit-billing-address.hbs +1 -1
- package/src/components/checkout-payment-details-v2.hbs +6 -1
- package/src/components/share-list-modal-without-social-icons.hbs +1 -1
- package/src/components/share-list-modal.hbs +1 -1
- package/src/js/emulation/mock.js +2394 -2348
- package/src/js/emulation/tracking-emulation.js +38 -0
- package/src/js/page/bloomreach-widget/bloomreach-widget-tracking.js +87 -0
- package/src/js/page/bloomreach-widget/complete-your-project-widget.js +65 -0
- package/src/js/page/bloomreach-widget/why-not-add-widget.js +34 -2
- package/src/js/page/checkout-payment-details.js +10 -0
- package/src/js/page/utils/data-layer.js +9 -0
- package/src/page_payment-details-billie-registered-only.html +76 -0
- package/src/page_payment-details-billie-unregistered-only.html +76 -0
- package/src/sitemap.html +12 -0
package/Readme.md
CHANGED
|
@@ -6,7 +6,6 @@ This project requires 14 version of node.js. From now on we are using yarn as pa
|
|
|
6
6
|
## Commit Guidelines
|
|
7
7
|
This project is now using the semantic-release npm plug-in to control versioning. This means that it will automatically bump the version numbers when the CI build occurs.
|
|
8
8
|
The decision on whether this is a patch, feature or breaking (b.f.p) release is based upon the GIT commit messages. We are using the [Angular Commit Message Conventions](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines)
|
|
9
|
-
|
|
10
9
|
| Commit message | Release type |
|
|
11
10
|
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
|
|
12
11
|
| `fix(pencil): stop graphite breaking when too much pressure applied` | Patch Release |
|
|
@@ -232,12 +231,9 @@ While using breakpoints we should use right order of its placement:
|
|
|
232
231
|
}
|
|
233
232
|
|
|
234
233
|
```
|
|
235
|
-
|
|
236
234
|
* Preferable way is to use one way of breakpoints direction: -up or -down, and to use them both only in exceptional cases"
|
|
237
|
-
|
|
238
235
|
* -only breakpoints should be placed only after group of -up or -down
|
|
239
236
|
|
|
240
|
-
|
|
241
237
|
## Js
|
|
242
238
|
|
|
243
239
|
... to be added
|