Merge branch 'dev' into master-2.2.0

Author: alexcjohnson

.circleci/config.yml

@@ -59,6 +59,14 @@ jobs:
             mkdir dash-package && cp dist/*.tar.gz dash-package/dash-package.tar.gz
             ls -la dash-package
           no_output_timeout: 30m
+      - run:
+          name: Display npm errors and exit on failed builds
+          command: |
+            if [ -d "/home/circleci/.npm/_logs" ]
+            then
+              cat /home/circleci/.npm/_logs/*
+              exit 1
+            fi
       - save_cache:
           key: dep-{{ checksum ".circleci/config.yml" }}-{{ checksum "ver.txt" }}-{{ checksum "requires-all.txt" }}
           paths:
@@ -111,7 +119,7 @@ jobs:
             . venv/bin/activate
             set -eo pipefail
             pip install -e . --progress-bar off && pip list | grep dash
-            npm install --production && npm run initialize
+            npm install npm run initialize
             npm run build
             npm run lint
       - run:

.husky/pre-commit

@@ -1 +1,3 @@
-npm run lint
+npm run lint && \
+(cd components/dash-core-components && npm run lint) && \
+(cd components/dash-table && npm run lint)

CHANGELOG.md

@@ -2,6 +2,29 @@
 All notable changes to `dash` will be documented in this file.
 This project adheres to [Semantic Versioning](https://semver.org/).
 
+## [2.2.0] - 2022-02-18
+
+### Added
+- [#1923](https://github.com/plotly/dash/pull/1923):
+  - `dash.get_relative_path`
+  - `dash.strip_relative_path`
+  - `dash.get_asset_url`
+  This is similar to `dash.callback` where you don't need the `app` object. It makes it possible to use these
+  functions in the `pages` folder of a multi-page app without running into the circular `app` imports issue.
+
+### Updated
+- [#1911](https://github.com/plotly/dash/pull/1911) Upgrade Plotly.js to v2.9.0 (from v2.8.3).
+  - Adds `ticklabelstep` to axes to reduce tick labels while still showing all ticks.
+  - Displays the plotly.js version when hovering on the modebar. This helps debugging situations where there might be multiple sources of plotly.js, for example `/assets` vs the versions built into `dcc` or `ddk`.
+
+- [#1930](https://github.com/plotly/dash/pull/1930) Upgrade JavaScript dependencies across renderer and all components.
+
+### Fixed
+- [#1932](https://github.com/plotly/dash/pull/1932) Fixes several bugs:
+  - Restores compatibility with IE11 [#1925](https://github.com/plotly/dash/issues/1925)
+  - Restores `style_header` text alignment in Dash Table [#1914](https://github.com/plotly/dash/issues/1914)
+  - Clears the unneeded `webdriver-manager` requirement from `dash[testing]` [#1919](https://github.com/plotly/dash/issues/1925)
+
 ## [2.1.0] - 2022-01-28
 
 ### Changed

CONTRIBUTING.md

@@ -14,14 +14,21 @@ $ python3 -m venv .venv/dev
 # on some linux / mac environments, use `.` instead of `source`
 $ source .venv/dev/bin/activate
 # install dash and dependencies
-$ pip install -e .[testing,dev]  # in some shells you need \ to escape []
+$ pip install -e .[ci,dev,testing,celery,diskcache]  # in some shells you need \ to escape []
 $ npm install
 # this script will build the dash-core-components, dash-html-components, dash-table,
 # and renderer bundles; this will build all bundles from source code in their
 # respective directories. The only true source of npm version is defined
 # in package.json for each package.
+#
 $ npm run build  # runs `renderer build` and `npm build` in dcc, html, table
 # build and install components used in tests
+#
+# Alternatively one could run part of the build process e.g.
+$ dash-update-components "dash-core-components"
+# to only build dcc when developing dcc
+# But when you first clone check out a new branch, you must run the full build as above.
+#
 $ npm run setup-tests.py # or npm run setup-tests.R
 # you should see dash points to a local source repo
 $ pip list | grep dash