Merge branch 'main' of https://github.com/mckinsey/vizro into qa/vizr…

…o_ai_ui_tests

� Conflicts:
�	.github/workflows/vizro-qa-tests-trigger.yml
�	vizro-core/hatch.toml

.github/actions/failed-artifacts-and-slack-notifications/action.yml

@@ -0,0 +1,31 @@
+name: "Create artifacts and slack notifications"
+description: "Creates failed artifacts with screenshots and sends slack notifications if build failed"
+
+runs:
+  using: "composite"
+  steps:
+    - name: Copy failed screenshots
+      shell: bash
+      run: |
+        mkdir /home/runner/work/vizro/vizro/vizro-core/failed_screenshots/
+        cd /home/runner/work/vizro/vizro/vizro-core/
+        cp *.png failed_screenshots
+
+    - name: Archive production artifacts
+      uses: actions/upload-artifact@v4
+      with:
+        name: Failed screenshots
+        path: |
+          /home/runner/work/vizro/vizro/vizro-core/failed_screenshots/*.png
+
+    - name: Send custom JSON data to Slack
+      id: slack
+      uses: slackapi/[email protected]
+      with:
+        payload: |
+          {
+            "text": "${{ env.TESTS_NAME }} build result: ${{ job.status }}\nBranch: ${{ github.head_ref }}\n${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}"
+          }
+      env:
+        SLACK_WEBHOOK_URL: ${{ env.SLACK_WEBHOOK_URL }}
+        SLACK_WEBHOOK_TYPE: INCOMING_WEBHOOK

.github/pull_request_template.md

@@ -6,8 +6,8 @@
 
 - [ ] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":
 
-  - I submit this contribution under the [Apache 2.0 license](https://www.apache.org/licenses/LICENSE-2.0.txt) and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
-  - I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorized to submit this contribution on behalf of the original creator(s) or their licensees.
-  - I certify that the use of this contribution as authorized by the Apache 2.0 license does not violate the intellectual property rights of anyone else.
-  - I have not referenced individuals, products or companies in any commits, directly or indirectly.
-  - I have not added data or restricted code in any commits, directly or indirectly.
+    - I submit this contribution under the [Apache 2.0 license](https://www.apache.org/licenses/LICENSE-2.0.txt) and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
+    - I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorized to submit this contribution on behalf of the original creator(s) or their licensees.
+    - I certify that the use of this contribution as authorized by the Apache 2.0 license does not violate the intellectual property rights of anyone else.
+    - I have not referenced individuals, products or companies in any commits, directly or indirectly.
+    - I have not added data or restricted code in any commits, directly or indirectly.

.github/workflows/test-e2e-component-library-vizro-core.yml

@@ -0,0 +1,45 @@
+name: e2e tests of component library for Vizro
+
+defaults:
+  run:
+    working-directory: vizro-core
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches:
+      - main
+
+env:
+  PYTHONUNBUFFERED: 1
+  FORCE_COLOR: 1
+  PYTHON_VERSION: "3.12"
+
+jobs:
+  test-e2e-component-library-vizro-core:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ env.PYTHON_VERSION }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ env.PYTHON_VERSION }}
+
+      - name: Install Hatch
+        run: pip install hatch
+
+      - name: Show dependency tree
+        run: hatch run pip tree
+
+      - name: Run e2e component library tests
+        run: hatch run test-e2e-component-library
+
+      - name: Create artifacts and slack notifications
+        if: failure()
+        uses: ./.github/actions/failed-artifacts-and-slack-notifications
+        env:
+          TESTS_NAME: Vizro e2e component library tests
+          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

.github/workflows/test-integration-vizro-ai.yml

@@ -144,7 +144,7 @@ jobs:
 
       - name: Send custom JSON data to Slack
         id: slack
-        uses: slackapi/slack-github-action@v1.27.0
+        uses: slackapi/slack-github-action@v2.0.0
         if: failure()
         with:
           payload: |

.github/workflows/test-score-vizro-ai.yml

@@ -94,7 +94,7 @@ jobs:
 
       - name: Send custom JSON data to Slack
         id: slack
-        uses: slackapi/slack-github-action@v1.27.0
+        uses: slackapi/slack-github-action@v2.0.0
         if: failure()
         with:
           payload: |

.pre-commit-config.yaml

@@ -34,8 +34,9 @@ repos:
         description: Linter for json, yaml, md, css and more
         entry: prettier --write --ignore-unknown
         language: node
-        "types": [text]
+        types: [text]
         additional_dependencies: ["[email protected]"]
+        exclude_types: [markdown]
 
   - repo: https://github.com/macisamuele/language-formatters-pre-commit-hooks
     rev: v2.14.0
@@ -44,15 +45,15 @@ repos:
         args: [--autofix]
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.7.2
+    rev: v0.8.1
     hooks:
       - id: ruff
         args: [--fix]
         exclude: "vizro-core/examples/scratch_dev/app.py"
       - id: ruff-format
 
   - repo: https://github.com/PyCQA/bandit
-    rev: 1.7.10
+    rev: 1.8.0
     hooks:
       - id: bandit
         args: [-c, pyproject.toml, -ll]
@@ -83,16 +84,19 @@ repos:
           - [email protected]
         args: ["--fix"]
 
-  - repo: https://github.com/errata-ai/vale
-    rev: v3.8.0
+  - repo: https://github.com/executablebooks/mdformat
+    rev: 0.7.18
     hooks:
-      - id: vale
-        args: [--config=.vale/.vale.ini]
-        # There's no way to automatically convert vale suggestions/warnings to errors, and so they won't appear at all unless
-        # there's an error raised.
-        # pre-commit's verbose mode means that suggestions and warnings are always shown even if there's no error raised.
-        # See https://github.com/errata-ai/vale/issues/575.
-        verbose: true
+      - id: mdformat
+        args:
+          [
+            --ignore-missing-references,
+            --wrap=no,
+            --align-semantic-breaks-in-lists,
+          ]
+        exclude: ^vizro-core/docs/pages/API-reference|^vizro-ai/docs/pages/API-reference|vizro-core/docs/pages/user-guides/custom-components.md|^vizro-core/changelog.d|^vizro-ai/changelog.d
+        additional_dependencies:
+          - mdformat-mkdocs[recommended]==3.1.1
 
 # Configuration for https://pre-commit.ci/.
 ci:
@@ -108,4 +112,3 @@ ci:
     - codespell
     - bandit
     - mypy
-    - vale

.stylelintrc

@@ -8,6 +8,7 @@
     "color-function-notation": "legacy",
     "alpha-value-notation": "number",
     "color-hex-length": "long",
-    "selector-not-notation": null
+    "selector-not-notation": null,
+    "declaration-property-value-no-unknown": true
   }
 }

.vale/styles/Microsoft/Acronyms.yml

@@ -39,6 +39,7 @@ exceptions:
   - LESS
   - LLDB
   - LLM
+  - MIT
   - NET
   - NOTE
   - NVDA

.vale/styles/Microsoft/Headings.yml

@@ -71,6 +71,8 @@ exceptions:
   - Kubernetes Service
   - Lambda
   - LangChain
+  - LangFuse
+  - LangSmith
   - Linux
   - MySQL
   - Notebook

.vale/styles/Microsoft/ignore.txt

@@ -19,6 +19,7 @@ formatters
 fsspec
 globals
 Globals
+interpretability
 Kaggle
 namespace
 namespaces

CODE_OF_CONDUCT.md

@@ -2,17 +2,11 @@
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socioeconomic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socioeconomic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
 ## Our Standards
 
-Examples of behavior that contributes to creating a positive environment
-include:
+Examples of behavior that contributes to creating a positive environment include:
 
 - Using welcoming and inclusive language
 - Being respectful of differing viewpoints and experiences
@@ -22,57 +16,34 @@ include:
 
 Examples of unacceptable behavior by participants include:
 
-- The use of sexualised language or imagery and unwelcome sexual attention or
-  advances
+- The use of sexualised language or imagery and unwelcome sexual attention or advances
 - Trolling, insulting/derogatory comments, and personal or political attacks
 - Public or private harassment
-- Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ## Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 
 **Investigation Timeline:** The project team will make all reasonable efforts to initiate and conclude the investigation in a timely fashion. Depending on the type of investigation the steps and timeline for each investigation will vary.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
 
-[homepage]: https://www.contributor-covenant.org
+For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
 
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

@@ -1,4 +1,3 @@
 # Contributing
 
-Contributions of all experience levels are welcome! If you're interested in making a contribution,
-please refer to our [contributing guide](https://vizro.readthedocs.io/en/stable/pages/explanation/contributing/) for more information.
+Contributions of all experience levels are welcome! If you're interested in making a contribution, please refer to our [contributing guide](https://vizro.readthedocs.io/en/stable/pages/explanation/contributing/) for more information.

README.md

@@ -11,19 +11,13 @@
 
 <div align="center" markdown="1">
 
-[![Python version](https://img.shields.io/badge/python-3.9%20%7C%203.10%20%7C%203.11%20%7C%203.12%20%7C%203.13-blue.svg)](https://pypi.org/project/vizro/)
-[![PyPI version](https://badge.fury.io/py/vizro.svg)](https://badge.fury.io/py/vizro)
-[![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://github.com/mckinsey/vizro/blob/main/LICENSE.md)
-[![Documentation](https://readthedocs.org/projects/vizro/badge/?version=stable)](https://vizro.readthedocs.io/)
-[![OpenSSF Best Practices](https://www.bestpractices.dev/projects/7858/badge)](https://www.bestpractices.dev/projects/7858)
+[![Python version](https://img.shields.io/badge/python-3.9%20%7C%203.10%20%7C%203.11%20%7C%203.12%20%7C%203.13-blue.svg)](https://pypi.org/project/vizro/) [![PyPI version](https://badge.fury.io/py/vizro.svg)](https://badge.fury.io/py/vizro) [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://github.com/mckinsey/vizro/blob/main/LICENSE.md) [![Documentation](https://readthedocs.org/projects/vizro/badge/?version=stable)](https://vizro.readthedocs.io/) [![OpenSSF Best Practices](https://www.bestpractices.dev/projects/7858/badge)](https://www.bestpractices.dev/projects/7858)
 
 </div>
 
 <div align="center" markdown="1">
 
-<a href="https://vizro.readthedocs.io/en/stable/" target="_blank">Documentation </a> |
-<a href="https://vizro.readthedocs.io/en/stable/pages/tutorials/first_dashboard/" target="_blank">Get Started </a> |
-<a href="http://vizro.mckinsey.com/" target="_blank">Vizro examples gallery</a>
+<a href="https://vizro.readthedocs.io/en/stable/" target="_blank">Documentation </a> | <a href="https://vizro.readthedocs.io/en/stable/pages/tutorials/first_dashboard/" target="_blank">Get Started </a> | <a href="http://vizro.mckinsey.com/" target="_blank">Vizro examples gallery</a>
 
 </div>
 
@@ -108,9 +102,7 @@ You can see Vizro in action by clicking on the following image or by visiting [t
 
 ## Visual vocabulary
 
-Our visual vocabulary dashboard helps you to select and create various types of charts. It helps you decide when to use
-each chart type, and offers sample Python code to create these charts with [Plotly](https://plotly.com/python/) and
-embed them into a Vizro dashboard.
+Our visual vocabulary dashboard helps you to select and create various types of charts. It helps you decide when to use each chart type, and offers sample Python code to create these charts with [Plotly](https://plotly.com/python/) and embed them into a Vizro dashboard.
 
 <a href="https://vizro-demo-visual-vocabulary.hf.space">
 <img src="https://raw.githubusercontent.com/mckinsey/vizro/main/.github/images/visual_vocabulary.png" width="550">

pyproject.toml

@@ -14,7 +14,7 @@ exclude_dirs = ["tests"]
 [tool.codespell]
 builtin = "clear,rare,en-GB_to_en-US"
 ignore-words-list = "grey,ned,sav,Thur"
-skip = "*.min.css.map,*.min.css,.vale/*, *assets/*"
+skip = "*.min.css.map,*.min.css,.vale/*, *assets/*,.github/*"
 
 [tool.mypy]
 # strict checks : strict = true

vizro-ai/CHANGELOG.md

@@ -141,5 +141,4 @@ See the fragment files in the [changelog.d directory](https://github.com/mckinse
 
 ## Highlights ✨
 
-- Initial release of Vizro-AI package. Vizro-AI is a tool for generating data
-  visualizations. ([#138](https://github.com/mckinsey/vizro/pull/138))
+- Initial release of Vizro-AI package. Vizro-AI is a tool for generating data visualizations. ([#138](https://github.com/mckinsey/vizro/pull/138))