updating certification branch (microsoft#154)

* New translations (microsoft#112)

* Microsoft mandatory file (microsoft#117)

Co-authored-by: microsoft-github-policy-service[bot] <77245923+microsoft-github-policy-service[bot]@users.noreply.github.com>

* Update codeql-analysis.yml

* Dev (microsoft#153)

* Update timeline to use new formatting model API (5.1+) (microsoft#137)

* Add new formatting model units

* Update capabilities.json to new formatting model API

* Update version to 2.5.0

* Refactor Calendar into using interfaces

* Upgrade to new formatting model API

* Remove jquery, fix tests

* Migrate from puppeteer to playwright-chromium

* Split d3 into submodules like d3-selection

* Update dependencies

Previously visual didn't work with node v20.10.0,
but after updating the dependencies it works now.

* Set default value "false" for ScrollAutoAdjustment

* Fix top level slices to display "show" button on the cards

* Add stroke color and stroke width settings

* Add cursor color settings

* Add an option to specify the width, height manually

* Add scroll behavior

When scrolling on the cell it increases/decreases the date period.

* Add cell gap setting

* Revert "Add scroll behavior"

This reverts commit 3a0e970.

* Decrease min cell width. Add missing localization keys.

* Fix build status in README.md

* Use 4 digit number in version

* Update build.yml to run audit, outdated, linter

* Rename ambiguous topLevelSlice to show field. Revert MinCellWidth to fix a breaking change.

* Fix the resizing issue when enabling manual sizing.

When enabling manual sizing width and height of the cell is changed to the last saved by the user. Instead, the expected behavior is so width and height should be the same as before enabling manual sizing. It requires persisting current width and height of cells, but it triggers an additional update.

* Fix uneven stroke width around cells

When increasing stroke-width around the cells the height of the cell should be decreasing, otherwise the stroke is uneven.

* Fix vertical cursor shift when changing stroke width

* Update packages

* Fix npm vulnerabilities

* Remove core-js

* Update powerbi-visuals-api to 5.7.0

* Fix the issue with replacing old Timeline visual with newer version (microsoft#138)

* Add "Visual_Short_Description", "Visual_Long_Description" localization keys

* Fix the issue with upgrading the visual version inside the report

When user replaces the visual with new version the visual didn't render because some ItemDropDown values were not set.

* Fix eslint errors

* New translations

* Fix error with rendering when ItemDropDown values are undefined (microsoft#139)

* Fix error with rendering when ItemDropDown values are undefined

* Fix tests

* New translations

* Fix backwards compatibility (microsoft#143)

* Fix error with rendering when ItemDropDown values are undefined

* Fix tests

* Set topLevelSlice for "Cursor", "First Day of Week" formatting settings cards

* Update API to 5.8.0

* Fix height and width calculation when enableManualSizing is enabled

* Limit max text size in range header and labels

* Rollback capabilities.json to previous configuration to keep backwards compatibility

* Update packages

Bump version to 2.5.0.0

* Remove jquery

* Update GitHub actions to use node 18, 20

* Add TimelineSettingsModel.ts

* Refactor calendar interfaces

* Migrate to formatting model

* Add visual short and long description localization keys

* Fix granularity value backwards compatibility (use numbers instead of string)

* Add cursor formatting settings

* Add "Cells" card settings: stroke width and gap width

* Add formatting setting to manually resize cell height and width

* Split D3 into submodules like d3-selection

* Update packages

* Update API to 5.9.0

* Refactor event handlers into behavior.ts

* Refactor behavior.ts into static

* Fix karma.config

* Fix bugs with click handler and selecting period (microsoft#148)

* Disable "Calendar" and "First day of week" settings when WeekStandard is set to IS0 8601

* Fix cell click handler (passed invalid selected index)

* Fix uninitialized start date when date from filters is less than date from DataView

* Increase font max size for range header to 40

* Update outdated packages

* New translations

* New translations

* New translations

---------

Co-authored-by: adiletelf <[email protected]>
Co-authored-by: pbicvloc <[email protected]>

---------

Co-authored-by: pbicvloc <[email protected]>
Co-authored-by: microsoft-github-policy-service[bot] <77245923+microsoft-github-policy-service[bot]@users.noreply.github.com>
Co-authored-by: adiletelf <[email protected]>

.editorconfig

@@ -8,7 +8,7 @@ trim_trailing_whitespace = true
 indent_style = space
 
 [*.json]
-indent_size = 2
+indent_size = 4
 
 [*.less]
 indent_size = 4

.github/workflows/build.yml

@@ -1,13 +1,13 @@
-# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
+# This workflow will do a clean installation of node dependencies, build the source code and run tests across different versions of node
 # For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
 
 name: build
 
 on:
   push:
-    branches: [ master ]
+    branches: [ main, dev, certification ]
   pull_request:
-    branches: [ master ]
+    branches: [ main, dev, certification ]
 
 jobs:
   build:
@@ -16,7 +16,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [12.x]
+        node-version: [18.x, 20.x]
 
     steps:
     - uses: actions/checkout@v2
@@ -25,7 +25,12 @@ jobs:
       with:
         node-version: ${{ matrix.node-version }}
     - run: npm ci
-    - run: npm run lint
+    - run: npm audit
+      continue-on-error: true
+    - run: npm outdated
+      continue-on-error: true
+    - run: npm run eslint
+    - run: npm run package
     - run: npm test
       env:
         CI: true

.github/workflows/codeql-analysis.yml

@@ -1,67 +1,49 @@
-# For most projects, this workflow file will not need changing; you simply need
-# to commit it to your repository.
-#
-# You may wish to alter this file to override the set of languages analyzed,
-# or to provide custom queries or build logic.
-#
-# ******** NOTE ********
-# We have attempted to detect the languages in your repository. Please check
-# the `language` matrix defined below to confirm you have the correct set of
-# supported CodeQL languages.
-#
 name: "CodeQL"
 
 on:
   push:
-    branches: [ master ]
+    branches: [main, dev, certification]
   pull_request:
-    # The branches below must be a subset of the branches above
-    branches: [ master ]
+    branches: [main, dev, certification]
   schedule:
-    - cron: '22 23 * * 1'
+    - cron: '0 0 * * 3'
 
 jobs:
   analyze:
     name: Analyze
     runs-on: ubuntu-latest
+    timeout-minutes: 60
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
 
     strategy:
       fail-fast: false
       matrix:
-        language: [ 'javascript' ]
-        # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ]
-        # Learn more:
-        # https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed
-
+        language: ['typescript']
+
     steps:
     - name: Checkout repository
-      uses: actions/checkout@v2
+      uses: actions/checkout@v4
+      with:
+        fetch-depth: 2
+
+    - name: Use Node.js 18
+      uses: actions/setup-node@v2
+      with:
+        node-version: 18.x
+
+    - name: Install Dependencies
+      run: npm ci
 
-    # Initializes the CodeQL tools for scanning.
     - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
+      uses: github/codeql-action/init@v3
       with:
         languages: ${{ matrix.language }}
-        # If you wish to specify custom queries, you can do so here or in a config file.
-        # By default, queries listed here will override any specified in a config file.
-        # Prefix the list here with "+" to use these queries and those in the config file.
-        # queries: ./path/to/local/query, your-org/your-repo/queries@main
 
-    # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
-    # If this step fails, then you should remove it and run the build manually (see below)
     - name: Autobuild
-      uses: github/codeql-action/autobuild@v1
-
-    # ℹ️ Command-line programs to run using the OS shell.
-    # 📚 https://git.io/JvXDl
-
-    # ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
-    #    and modify them (or add more) to build your code if your project
-    #    uses a compiled language
-
-    #- run: |
-    #   make bootstrap
-    #   make release
+      uses: github/codeql-action/autobuild@v3
 
     - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@v1
+      uses: github/codeql-action/analyze@v3

.gitignore

@@ -9,3 +9,6 @@ coverage
 webpack.statistics.html
 webpack.statistics.dev.html
 webpack.statistics.prod.html
+
+## JetBrains
+.idea/

CHANGELOG.md

@@ -1,3 +1,34 @@
+## 2.5.4
+* Disable "Calendar" and "First day of week" settings when WeekStandard is set to IS0 860
+* Fix uninitialized start date when date from filters is less than date from DataView
+* Fix cell click handler (passed invalid selected index)
+
+## 2.5.3
+* Update API to 5.9.0
+* Fix npm vulnerabilities
+* Refactor event handlers into behavior.ts
+
+## 2.5.2
+* Fix backwards compatibility with 2.4.0
+* Packages update
+
+## 2.5.1
+* powerbi-visuals-api was updated to 5.8.0
+* Packages update
+
+
+## 2.5.0
+* powerbi-visuals-api was updated to 5.7.0
+* Updated to new formatting model api provided
+* Migrate from puppeteer to playwright
+* Split d3 package into d3-selection, d3-shape, d3-drag, d3-array. Update d3 to v6
+* Remove lodash, jquery, tslint, ts-node, istanbul-reporter
+* Update dependencies
+* Add missing localization keys
+* Add cursor color settings
+* Add stroke color settings
+* Update build.yml to use node 18, 20
+
 ## 2.3.0
 * A new option group "Weeks Determination Standards" containing a list of two items where the first one enables US weeks numbering (default) and the second one enables ISO 8601 weeks numbering
 

README.md

@@ -1,5 +1,5 @@
 # Timeline Slicer
-[![Build Status](https://travis-ci.org/Microsoft/powerbi-visuals-timeline.svg?branch=master)](https://travis-ci.org/Microsoft/powerbi-visuals-timeline) [![Coverage Status](https://coveralls.io/repos/github/Microsoft/powerbi-visuals-timeline/badge.svg?branch=master)](https://coveralls.io/github/Microsoft/powerbi-visuals-timeline?branch=master)
+[![build status](https://github.com/microsoft/powerbi-visuals-timeline/actions/workflows/build.yml/badge.svg?branch=main)](https://github.com/microsoft/powerbi-visuals-timeline/actions/workflows/build.yml)
 
 > Graphical date range selector to use for filtering dates
 
@@ -11,11 +11,11 @@ The Timeline slicer is a graphical date range selector used as a filtering compo
 
 How often do you have to filter your data for a date range or at higher level such as month or quarter? Every single time. Right? Filtering is pain when you have to click through large numbers of date values to select the range you want. Changing the filter granularity from months, the quarters and years on the fly is super tedious. Well, it used to be super tedious.
 
-The Timeline slicer is going to make this experience a breeze. With this simple slider control for dates, all you need to do, is just click and drag to the range that you want. You can also switch to a Year, Quarter or Month view to 
+The Timeline slicer is going to make this experience a breeze. With this simple slider control for dates, all you need to do, is just click and drag to the range that you want. You can also switch to a Year, Quarter or Month view to
 select ranges even at a higher level than dates.
 
 You can simply click on the slicer to select a single value or click the edge and drag it to the range that you want.
 
 You can also change the background & selection color and number of other formatting options to control the look-n-feel. SHIFT+Click also works for selecting a range.
 
-See also [Timeline Slicer at Microsoft AppSource](https://appsource.microsoft.com/en-us/product/power-bi-visuals/WA104380786)
+See also [Timeline Slicer at Microsoft AppSource](https://appsource.microsoft.com/en-us/product/power-bi-visuals/WA104380786)

SECURITY.md

@@ -0,0 +1,41 @@
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.8 BLOCK -->
+
+## Security
+
+Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
+
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
+
+## Reporting Security Issues
+
+**Please do not report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
+
+If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
+
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+  * Full paths of source file(s) related to the manifestation of the issue
+  * The location of the affected source code (tag/branch/commit or direct URL)
+  * Any special configuration required to reproduce the issue
+  * Step-by-step instructions to reproduce the issue
+  * Proof-of-concept or exploit code (if possible)
+  * Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
+If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd).
+
+<!-- END MICROSOFT SECURITY.MD BLOCK -->