Merge branch 'main' of github.com:exadel-inc/esl into main-beta

Author: ala-n

.github/workflows/pages.yml

@@ -9,13 +9,29 @@ on:
 env:
   node-version: 18.x
 
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allows only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
 jobs:
-  deploy-gh-pages:
-    name: Build and Deploy
+  # Build job
+  build-gh-pages:
+    name: Build
     runs-on: ubuntu-latest
-
     steps:
-      - uses: actions/checkout@v3
+      - name: Checkout
+        uses: actions/checkout@v3
+      - name: Setup Pages
+        id: pages
+        uses: actions/configure-pages@v3
       - name: Use Node v${{ env.node-version }}
         uses: actions/setup-node@v3
         with:
@@ -27,8 +43,23 @@ jobs:
         run: npm run build
       - name: Build Site
         run: npm run build -w pages
-      - name: Deploy
-        uses: JamesIves/github-pages-deploy-action@v4
+        env:
+          SITE_BASE_URL: ${{ steps.pages.outputs.base_url }}
+          BUILD_VERSION: ${{ github.run_number }}
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v2
         with:
-          branch: gh-pages
-          folder: pages/dist
+          path: ./pages/dist
+
+  # Deployment job
+  deploy-gh-pages:
+    name: Deploy
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build-gh-pages
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v2

.github/workflows/release.yml

@@ -5,6 +5,7 @@ on:
     inputs:
       dryRun:
         type: boolean
+        default: true
         required: false
         description: 'Run in dry-run mode (no actual release)'
 

.releaserc.yml

@@ -49,7 +49,6 @@ plugins:
           - BREAKING CHANGE
           - BREAKING CHANGES
           - BREAKING-CHANGE
-          - BREAKING
 
   - - "@semantic-release/changelog"
     - changelogFile: CHANGELOG.md
@@ -62,6 +61,7 @@ plugins:
         - CHANGELOG.md
         - package.json
         - package-lock.json
+        - pages/package.json
       message: "chore(release): ${nextRelease.version} \n\n${nextRelease.notes}"
 
   - - "@semantic-release/github"

CHANGELOG.md

@@ -1,3 +1,27 @@
+# [4.12.0](https://github.com/exadel-inc/esl/compare/v4.11.0...v4.12.0) (2023-09-22)
+
+
+### Bug Fixes
+
+* **esl-tabs:** observe element resize instead of window using `ESLResizeObserverTarget` ([9dd4639](https://github.com/exadel-inc/esl/commit/9dd4639c6d937758725c5a4e9e444c6c78d31215))
+
+
+### Code Refactoring
+
+* **esl-event-listener:** restructure `esl-event-listener/core/targets` ([fbdb6c3](https://github.com/exadel-inc/esl/commit/fbdb6c335e9863fddb6a817a66689cc127356335))
+
+
+### Features
+
+* **esl-event-listener:** `ESLEventUtils.unsubscribe` implementation moved to internal `ESLEventListener.unsubscribe` ([eaa4204](https://github.com/exadel-inc/esl/commit/eaa42045c39f3cbb5f07568aab93b9bd2a6fba98))
+* **esl-event-listener:** add `SwipeEventTarget` to subscribe `swipe` events using `ESLEventListener` ([e7e69a2](https://github.com/exadel-inc/esl/commit/e7e69a257b74f985be0c191b8e722dcb124bc74c)), closes [#1809](https://github.com/exadel-inc/esl/issues/1809)
+* **esl-media:** support for lazy initialization by `lazy` attribute for `ESLMedia` ([f83d65a](https://github.com/exadel-inc/esl/commit/f83d65a91e064e6f8aa2ddc7f9cc4e8b49eacba5))
+
+
+### BREAKING CHANGES
+
+* **esl-event-listener:** (if there is references to internal files) `resize.adapter.ts`/`resize.adapter.event.ts` renamed to `resize.target.ts`/`resize.target.event.ts`
+
 # [4.11.0](https://github.com/exadel-inc/esl/compare/v4.10.0...v4.11.0) (2023-09-01)
 
 

build/bump.js

@@ -0,0 +1,19 @@
+const fs = require('fs');
+const path = require('path');
+const root = require('../package.json');
+
+const packagePath = path.resolve(process.cwd(), 'package.json');
+
+try {
+  const content = fs.readFileSync(packagePath, 'utf8');
+
+  const result = content.replace(
+    /"version": "(\d+)\.(\d+)\.(\d+)"/,
+    `"version": "${root.version}"`
+  );
+
+  fs.writeFileSync(packagePath, result, 'utf8');
+  console.log('Submodule version bumped to', root.version);
+} catch (err) {
+  console.error("Can not bump version: ", err);
+}

docs/COMMIT_CONVENTION.md

@@ -20,18 +20,18 @@ to be sure that you are following the commit convention.
 - allows categorizing commits by importance and goals
 
 ## FAQ
-- Why do ESL use commit convention?
+- Why does ESL use the commit convention?
     - It's important for us to have an automated process of RELEASE NOTES and CHANGELOG creation.
 - What if incorrect commits were added to my branch?
     - Try to reword your commit messages using
       [git rebase](https://google.gprivate.com/search.php?search?q=git+rebase+reword)
     - You can also squash (concat into one commit) your commits but that's not necessary,
       the most important point is that your final commit messages correctly define the
       type and have a detailed and clear description of the changes
-    - Just in case you can't fix up your git history, provide a noticeable comment 
-      to use GitHub Squash Merge. It's also will be nice if you write a commit summary 
-      to make have the ability to make a result commit faster.
-- Do I need to define a type for each of the commits in my feature?
+    - In case you can't fix your Git history, please add a conspicuous comment indicating
+      the use of GitHub Squash Merge. Additionally, it would be helpful if you could provide a commit summary
+      to expedite the process of creating a final commit.
+- Do I need to define a type for each commit in my feature?
     - Yes, you will need a type for each commit. But, be careful with the following situations:
         - **If the feature or bug changes are not released and already described by the first message - 
           make sure you are using style or refactor change type. Even, if you are fixing your previous commit, 
@@ -71,11 +71,11 @@ Type is a required part of the message, and it is limited by the following value
 | ci       | Continuous integration and deployment related changes |
 | perf     | Backward-compatible performance improvements |
 
-Type should be in a lowercase.
+The type should be in lowercase.
 
 ### Force minor version update
 
-You can increase importance of the patch changes to the minor using the `MINOR VERSION` marker in the message.
+You can increase the importance of the patch changes to the minor using the `MINOR VERSION` marker in the message.
 
 ### BREAKING CHANGES
 
@@ -99,11 +99,11 @@ BREAKING CHANGES:
 
 Scope is an optional but "nice to have" part of your commit message.
 
-Use scope to clarify changes area (module, component, feature or epic).
+Use a scope to clarify changes area (module, component, feature or epic).
 
 Scope should be placed in parentheses after type but before `:`.
 
-Scope should be compatibly short and in a lowercase.
+The scope should be compatibly short and in lowercase.
 
 ```text
 fix(esl-component): IE compatibility
@@ -113,12 +113,12 @@ fix(esl-component): IE compatibility
 
 ### \<subject\>
 
-Subject is the main part of commit message where you should describe your changes.
+The subject is the main part of the commit message where you should describe your changes.
 
 Subject text rules:
 - be informative
 - use imperative, present tense: “change” not “changed” nor “changes”
-- don't capitalize first letter
+- don't capitalize the first letter
 - no dot (.) at the end
 
 **NOT**:
@@ -131,26 +131,27 @@ feat: Component updated to the new base class.
 
 **BUT**
 ```text
-fix (esl-utils): IE compatibility for scroll type detection
+fix(esl-utils): IE compatibility for scroll type detection
 ```
 ```text
-feat (esl-popup): esl-popup component base structure 
+feat(esl-popup): esl-popup component base structure 
 ```
 
 ---
 
 ### \<body\>
 
-The body is optional part of commit message. 
-Body part can be used to provide details of commit changes or clarify the motivation for changes.
+The body is an optional part of a commit message. 
+It can be used to provide details about the changes made in the commit or to clarify the motivation behind the changes.
 
-The header and body are supposed to be separated by a blank line.
+The header and body should be separated by a blank line.
 
 ---
 
 ### \<footer\>
 
-The footer is optional lines to provide additional details like linking closed issues, mentioning contributors and so on.
+The footer is optional lines to provide additional details like linking closed issues, mentioning contributors, and so
+on.
 
 The body and footer are also should be separated by a blank line.
 

docs/PRIVACY_POLICY.md

@@ -0,0 +1,49 @@
+# Privacy Policy
+
+<a name="content"></a>
+
+This privacy policy covers Exadel Smart Library Website and its associated mirrors. We respect and protect the privacy of our users. This privacy policy tells you how we collect and use information.
+
+## What information do we collect?
+
+We do not collect any personal information from you that you do not volunteer. Users may visit and use our Website anonymously.
+
+## Do we use cookies?
+
+Yes. Cookies are small files that a site or its service provider transfers to your computer's hard drive through your browser (if you allow). These cookies enable the site to recognize your browser. You may refuse the use of cookies by selecting the appropriate settings on your browser however please note that if you do this you may not be able to use the full functionality offered here at our Website.
+
+We use cookies to understand and save your preferences for future visits and compile aggregate data about site traffic and site interaction so that we can offer better site experiences and tools in the future. We may contract with third-party service providers to assist us in better understanding our site visitors. These service providers are not permitted to use the information collected on our behalf except to help us conduct and improve our business.
+
+## Do we disclose any information to outside parties?
+
+We do not sell, trade, or otherwise transfer to outside parties any information. 
+
+## What about website analytics and social media?
+
+Our website uses Google Analytics, a service that transmits website traffic data to Google servers in the United States. Google Analytics does not identify individual users or associate your IP address with any other data held by Google. We use reports provided by Google Analytics to help us understand website traffic and webpage usage.
+
+By using the Exadel Smart Library Website, you consent to the processing of data about you by Google in the manner described in [Google's Privacy Policy](https://policies.google.com/privacy) and for the purposes set out above. You can opt out of Google Analytics if you disable or refuse the cookie, disable JavaScript, or use the opt-out service provided by Google. Be aware that if you disable JavaScript completely you will impact the normal functionality of our Website. You can disable JavaScript selectively for Google Analytics with extensions to your browser.
+
+Exadel Smart Library Website also uses interfaces with social media sites such as Facebook and LinkedIn. If you choose to "share" information from this Website through these services, you should review the privacy policy of that service. If you are a member of a social media site, the interfaces may allow the social media site to connect your visits to this site with other personal information.
+
+## Are there any third-party links?
+
+Occasionally, at our discretion, we may include or offer third-party products or services on our site. These third-party sites have separate and independent privacy policies. We therefore have no responsibility or liability for the content and activities of these linked sites. Nonetheless, we seek to protect the integrity of our Website and welcome any feedback about these sites.
+
+## Children's Online Privacy Protection Act Compliance
+
+Our site, products, and services are all directed to people who are at least 13 years old or older. If this server is in the USA, and you are under the age of 13, per the requirements of COPPA (Children's Online Privacy Protection Act), do not use this site.
+
+## Changes to this privacy policy
+
+We have the discretion to update this privacy policy at any time. When we do, we will revise the updated date at the bottom of this page. We encourage Users to frequently check this page for any changes to stay informed about how we are helping to protect the personal information we collect. You acknowledge and agree that it is your responsibility to review this privacy policy periodically and become aware of modifications.
+
+## Your acceptance of these terms
+
+By using our Website, you signify your acceptance of this policy and terms of service. If you do not agree to this policy, please do not use our Website. Your continued use of the Website following the posting of changes to this policy will be deemed your acceptance of those changes.
+
+## Contacting us
+
+If you have any questions about this privacy policy, the practices of our Website, or your dealings with our Website, please contact us.
+
+<time datetime="2023-09-15">09/15/23</time>