New Crowdin updates

.lgtm.yml

@@ -1,21 +1,17 @@
-
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements.  See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership.  The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License.  You may obtain a copy of the License at
-#
-#   http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-# KIND, either express or implied.  See the License for the
-# specific language governing permissions and limitations
-# under the License.
-
+#Licensed to the Apache Software Foundation (ASF) under one
+#or more contributor license agreements.  See the NOTICE file
+#distributed with this work for additional information
+#regarding copyright ownership.  The ASF licenses this file
+#to you under the Apache License, Version 2.0 (the
+#"License"); you may not use this file except in compliance
+#with the License.  You may obtain a copy of the License at
+#http://www.apache.org/licenses/LICENSE-2.0
+#Unless required by applicable law or agreed to in writing,
+#software distributed under the License is distributed on an
+#"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+#KIND, either express or implied.  See the License for the
+#specific language governing permissions and limitations
+#under the License.
 path_classifiers:
   test:
     - test
@@ -28,3 +24,4 @@ extraction:
     index:
       exclude:
         - dist
+wefwef: wef

som/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,98 @@
+name: Bug Report
+description: Report a bug to Apache ECharts
+title: "[Bug] "
+labels:
+  - bug
+body:
+  - 
+    type: markdown
+    attributes:
+      value: |
+        The issue list is reserved exclusively for bug reports and feature requests.
+
+        For usage questions, please use the following resources:
+
+        - Read the [docs](https://echarts.apache.org/option.html)
+        - Find in [examples](https://echarts.apache.org/examples/)
+        - Look for / ask questions on [Stack Overflow](https://stackoverflow.com/questions/tagged/echarts)
+
+        For non-technical support or general questions, you can email [dev@echarts.apache.org](mailto:dev@echarts.apache.org). And don't forget to subscribe to our [mailing list](https://echarts.apache.org/maillist.html) to get updated with the project.
+
+        Also try to search for your issue - it may have already been answered or even fixed in the development branch. However, if you find that an old, closed issue still persists in the latest version, you should open a new issue using the form below instead of commenting on the old issue.
+  - 
+    #- type: checkboxes
+    #attributes:
+    #label: Is there an existing issue for this?
+    #description: Please search to see if an issue already exists for the bug you encountered.
+    #options:
+    #- label: I have searched the existing issues
+    #required: true
+    type: input
+    attributes:
+      label: Version
+      description: |
+        Check if the issue is reproducible with the latest stable version of Apache ECharts.
+      placeholder: |
+        e.g. 5.2.2
+    validations:
+      required: true
+  - 
+    type: input
+    attributes:
+      label: Link to Minimal Reproduction
+      description: |
+        If the reproduction does not need a build setup, please provide a link to [Official Editor](https://echarts.apache.org/examples/editor.html), [JSFiddle](https://jsfiddle.net/plainheart/e46ozpqj/7/), [JSBin](https://jsbin.com/) or [CodePen](https://codepen.io/Ovilia/pen/dyYWXWM). If it requires a build setup, you can use [CodeSandbox](https://codesandbox.io/s/echarts-basic-example-template-mpfz1s) or provide a GitHub repo.
+        The reproduction should be **minimal** - i.e. it should contain only the bare minimum amount of code needed to show the bug.
+        Please do not just fill in a random link. The issue will be closed if no valid reproduction is provided. [Why?](https://antfu.me/posts/why-reproductions-are-required)
+    validations:
+      required: true
+  - 
+    type: textarea
+    attributes:
+      label: Steps to Reproduce
+      description: |
+        What do we need to do after opening your repo in order to make the bug happen? Clear and concise reproduction instructions are important for us to be able to triage your issue in a timely manner. Note that you can use [Markdown](https://guides.github.com/features/mastering-markdown/) to format lists and code.
+      placeholder: |
+        1. How do you create the chart.
+        2. What's the chart option
+        3. User interactions before the error happens.
+    validations:
+      required: true
+  - 
+    type: textarea
+    attributes:
+      label: Current Behavior
+      description: A concise description of what you're experiencing.
+    validations:
+      required: true
+  - 
+    type: textarea
+    attributes:
+      label: Expected Behavior
+      description: A concise description of what you expected to happen.
+    validations:
+      required: true
+  - 
+    type: textarea
+    attributes:
+      label: Environment
+      description: |
+        e.g.
+          - **OS**: macOS Monterey
+          - **Browser**: Chrome 96.0.4664.55
+          - **Framework** Vue@3
+      value: |
+        - OS:
+        - Browser:
+        - Framework:
+      render: markdown
+    validations:
+      required: false
+  - 
+    type: textarea
+    attributes:
+      label: Any additional comments?
+      description: |
+        e.g. some background/context of how you ran into this bug.
+    validations:
+      required: false

som/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+#contact_links:
+#- name: Apache ECharts Doc
+#url: https://echarts.apache.org/option.html
+#about: Please search question here before opening a new issue

som/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,38 @@
+name: Feature Request
+description: Request a new feature from Apache ECharts
+title: "[Feature] "
+labels:
+  - new-feature
+body:
+  - 
+    type: markdown
+    attributes:
+      value: |
+        The issue list is reserved exclusively for bug reports and feature requests.
+
+        For usage questions, please use the following resources:
+
+        - Read the [docs](https://echarts.apache.org/option.html)
+        - Find in [examples](https://echarts.apache.org/examples/)
+        - Look for / ask questions on [Stack Overflow](https://stackoverflow.com/questions/tagged/echarts)
+
+        For non-technical support or general questions, you can email [dev@echarts.apache.org](mailto:dev@echarts.apache.org). And don't forget to subscribe to our [mailing list](https://echarts.apache.org/maillist.html) to get updated with the project.
+
+        Also try to search for your issue - it may have already been answered or even fixed in the development branch. However, if you find that an old, closed issue still persists in the latest version, you should open a new issue using the form below instead of commenting on the old issue.
+  - 
+    type: textarea
+    attributes:
+      label: What problem does this feature solve?
+      description: |
+        Explain your use case, context, and rationale behind this feature request. More importantly, what is the end user experience you are trying to build that led to the need for this feature?
+
+        An important design goal of ECharts is keeping the API surface small and straightforward. In general, we only consider adding new features that solve a problem that cannot be easily dealt with using existing APIs (i.e. not just an alternative way of doing things that can already be done). The problem should also be common enough to justify the addition.
+    validations:
+      required: true
+  - 
+    type: textarea
+    attributes:
+      label: What does the proposed API look like?
+      description: Describe how you propose to solve the problem and provide code samples of how the API would work once implemented. Note that you can use [Markdown](https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to format your code blocks.
+    validations:
+      required: true

som/.github/workflows/ci.yml

@@ -0,0 +1,128 @@
+name: Node CI
+on:
+  pull_request:
+    types:
+      - opened
+      - reopened
+      - synchronize
+concurrency:
+  #Note that the `teardown-pr-preview` workflow needs the same group name
+  #to cancel the running `ci` workflows
+  group: '${{ github.workflow }}-${{ github.event.number }}'
+  cancel-in-progress: true
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version:
+          - 18.x
+    steps:
+      - 
+        name: Fetch commit count
+        env:
+          PR_COMMIT_COUNT: '${{ github.event.pull_request.commits }}'
+        run: |
+          echo "FETCH_DEPTH=$(($PR_COMMIT_COUNT + 1))" >> $GITHUB_ENV
+      - 
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: '${{ env.FETCH_DEPTH }}'
+      - 
+        name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v4
+        with:
+          node-version: '${{ matrix.node-version }}'
+      - 
+        name: Cache node modules
+        id: cache-dep
+        uses: actions/cache@v4
+        env:
+          cache-name: cache-node-modules
+        with:
+          path: node_modules
+          key: '${{ runner.os }}-lint-${{ env.cache-name }}-${{ hashFiles(''**/package-lock.json'') }}'
+      - 
+        name: Install dependencies
+        if: steps.cache-dep.outputs.cache-hit != 'true'
+        run: npm ci
+      - 
+        name: Collect changed files
+        run: |
+          mkdir ~/tmp/
+          git diff ${{ github.event.pull_request.base.sha }} ${{ github.sha }} --diff-filter=ACM --name-only --relative '*src/**/*.ts' > ~/tmp/changed_files
+          echo -e "Changed files: \n$(cat ~/tmp/changed_files)"
+      - 
+        name: Lint
+        run: npx eslint $(cat ~/tmp/changed_files)
+      - 
+        name: Check types
+        run: npm run checktype
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version:
+          - 18.x
+    steps:
+      - 
+        uses: actions/checkout@v4
+      - 
+        name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v4
+        with:
+          node-version: '${{ matrix.node-version }}'
+      - 
+        name: Cache node modules
+        id: cache-dep
+        uses: actions/cache@v4
+        env:
+          cache-name: cache-node-modules
+        with:
+          path: node_modules
+          key: '${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles(''**/package-lock.json'') }}'
+      - 
+        name: Install dependencies
+        if: steps.cache-dep.outputs.cache-hit != 'true'
+        run: npm ci
+      - 
+        name: Unit Test
+        run: npm run test
+      - 
+        name: Build release
+        run: npm run release
+      - 
+        name: Test generated DTS
+        run: npm run test:dts
+      - 
+        name: Pack npm tarball
+        if: '${{ github.repository_owner == ''apache'' }}'
+        id: pack-tarball
+        run: |
+          export PR_PREVIEW_DIR='echarts-pr-preview'
+          mkdir -p $PR_PREVIEW_DIR
+          npm pack -pack-destination $PR_PREVIEW_DIR
+          echo "PR_PREVIEW_DIR=$PR_PREVIEW_DIR" >> $GITHUB_ENV
+      - 
+        name: Save PR metadata and dist files
+        if: '${{ steps.pack-tarball.outcome == ''success'' }}'
+        id: save-pr-data
+        env:
+          PR_NUMBER: '${{ github.event.number }}'
+          PR_COMMIT_SHA: '${{ github.event.pull_request.head.sha }}'
+          PR_PREVIEW_DIR: '${{ env.PR_PREVIEW_DIR }}'
+        run: |
+          cd $PR_PREVIEW_DIR
+          echo $PR_NUMBER > ./pr_number
+          echo $PR_COMMIT_SHA > ./pr_commit_sha
+          find . -type f -regex ".*\.tgz" -exec tar xvzf {} \;
+          rm -f *.tgz
+          echo -e "Dist files: \n$(ls -l)"
+      - 
+        uses: actions/upload-artifact@v4
+        if: '${{ steps.save-pr-data.outcome == ''success'' }}'
+        with:
+          name: pr_preview
+          path: '${{ env.PR_PREVIEW_DIR }}'
+          retention-days: 1
+          if-no-files-found: error

som/.github/workflows/nightly-next.yml

@@ -0,0 +1,42 @@
+name: Publish Nightly Next
+on:
+  schedule:
+    - 
+      cron: '10 9 * * *' #After zrender nightly published
+  #committers can manually trigger with workflow_dispatch
+  workflow_dispatch: { }
+  repository_dispatch:
+    types: publish-nightly-next
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    if: '${{ github.repository_owner == ''apache'' }}'
+    strategy:
+      matrix:
+        node-version:
+          - 18.x
+    steps:
+      - 
+        uses: actions/checkout@v4
+        with:
+          ref: next
+      - 
+        name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v4
+        with:
+          registry-url: https://registry.npmjs.org/
+          node-version: '${{ matrix.node-version }}'
+      - 
+        name: Setup and publish nightly
+        run: |
+          node build/nightly/prepare.js --next
+          npm i zrender@npm:zrender-nightly@next
+          npm ci
+          npm ls zrender
+          node build/nightly/post.js
+          npm run release
+          npm run test
+          npm run test:dts
+          npm publish --tag next
+        env:
+          NODE_AUTH_TOKEN: '${{secrets.NPM_TOKEN}}'

som/.github/workflows/nightly.yml

@@ -0,0 +1,40 @@
+name: Publish Nightly
+on:
+  schedule:
+    - 
+      cron: '0 9 * * *' #After zrender nightly published
+  #committers can manually trigger with workflow_dispatch
+  workflow_dispatch: { }
+  repository_dispatch:
+    types: publish-nightly
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    if: '${{ github.repository_owner == ''apache'' }}'
+    strategy:
+      matrix:
+        node-version:
+          - 18.x
+    steps:
+      - 
+        uses: actions/checkout@v4
+      - 
+        name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v4
+        with:
+          registry-url: https://registry.npmjs.org/
+          node-version: '${{ matrix.node-version }}'
+      - 
+        name: Setup and publish nightly
+        run: |
+          node build/nightly/prepare.js
+          npm i zrender@npm:zrender-nightly
+          npm ci
+          npm ls zrender
+          node build/nightly/post.js
+          npm run release
+          npm run test
+          npm run test:dts
+          npm publish
+        env:
+          NODE_AUTH_TOKEN: '${{secrets.NPM_TOKEN}}'