Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
61 commits
Select commit Hold shift + click to select a range
bd767e2
fix(polar): support borderRadius for polar bars #17980
Ovilia Nov 30, 2022
5667432
fix(polar): forgot to commit a new file
Ovilia Nov 30, 2022
47b6407
fix(ssr): fix label doesn't show in line series when `ssr` is enabled.`
plainheart Dec 7, 2022
b0eeb41
chore(deps-dev): bump terser from 5.3.8 to 5.14.2
Dec 12, 2022
a9330a1
chore: update package-lock.json
plainheart Dec 12, 2022
88766b4
Merge pull request #18055 from neostfox/master
plainheart Dec 12, 2022
a29290a
chore: fix several typos
striezel Dec 14, 2022
b76eff2
Merge pull request #18061 from striezel-stash/several-typos
Ovilia Dec 14, 2022
4b4a732
fix(tree): change symbol type. close #17946
ChepteaCatalin Dec 15, 2022
6be45ba
Merge pull request #18070 from ChepteaCatalin/fix-17946
Ovilia Dec 16, 2022
d6ab9d4
Merge pull request #18032 from apache/fix-ssr-line
pissang Dec 20, 2022
1c57908
chore: fix a few typos
striezel Dec 25, 2022
c86e558
Merge pull request #18103 from striezel-stash/fix-small-typos
plainheart Dec 26, 2022
c5eb4fa
upload example
huangyulie Dec 27, 2022
843c1e8
Merge pull request #18115 from huangyulie/fix-auto-huangyulie
plainheart Dec 28, 2022
c91620e
chore: update notice year to 2023
plainheart Dec 31, 2022
eaa332b
Merge pull request #18128 from apache/update-notice-year
plainheart Dec 31, 2022
3e22c04
chore(deps): bump json5 from 2.1.3 to 2.2.3
dependabot[bot] Jan 6, 2023
27415e3
Merge pull request #18142 from apache/dependabot/npm_and_yarn/json5-2…
plainheart Jan 6, 2023
2d8bc8f
chore: fix few typos (#18203)
Aman1919 Jan 23, 2023
6af586f
<fix>(tooltip): fix alwaysShowContent doesn't work after leaving the …
Feb 1, 2023
376e455
<fix>(tooltip): fix alwaysShowContent doesn't work after leaving the …
Feb 2, 2023
ac64e3f
<fix>(tooltip): fix alwaysShowContent doesn't work after leaving the …
Feb 2, 2023
8401d1a
fix(markArea): markArea range in bar series #18130
Ovilia Feb 2, 2023
9335a76
fix(sunburst): `radial` rotation label might upside down
susiwen8 Feb 4, 2023
8120aab
docs: fix a lot of grammatical errors in CONTRIBUTING.md (#18244)
Shaheer-Ahmd Feb 5, 2023
da29a8d
fix(dataset): object source contains `length` breaks render
susiwen8 Feb 15, 2023
fc2be18
feat(i18n): add Vietnamese(vi_VN) translation (#18279)
nghiepdev Feb 16, 2023
9191ab2
Merge pull request #18276 from susiwen8/18050
Ovilia Feb 16, 2023
3941fc9
fix(sunburst): adjust label rotation
susiwen8 Feb 17, 2023
19c3c9d
<fix>(tooltip): fix alwaysShowContent doesn't work after leaving the …
Feb 21, 2023
c206dc3
chore: simplify code
susiwen8 Feb 22, 2023
6d1f491
chore: ignore files about 'contributing' when publishing to npm (#18301)
fullmooooon Feb 23, 2023
dbec96f
Merge pull request #18240 from susiwen8/#18023
Ovilia Feb 24, 2023
a208201
fix(type): fix `treePathInfo` is missing in the type of sunburst form…
plainheart Feb 25, 2023
dc3a694
chore: merge
Ovilia Feb 27, 2023
d5ea937
fix(markArea): fix situations when dims is not defined
Ovilia Feb 27, 2023
0e2954c
Merge pull request #18221 from jianghaoran116/fix-18111
Ovilia Mar 3, 2023
710e79d
test: add test case for markers
Ovilia Mar 3, 2023
9c743be
Merge pull request #18310 from apache/fix/sunburst-types
plainheart Mar 5, 2023
dca62c9
feat: support bar background borderRadius
Ovilia Mar 6, 2023
e02ca38
style(marker): improve code
Ovilia Mar 6, 2023
50641db
Merge branch 'master' into fix-17980
Ovilia Mar 6, 2023
2752bea
Merge pull request #18229 from apache/fix-18130
Ovilia Mar 6, 2023
baa57b0
Merge pull request #17995 from apache/fix-17980
plainheart Mar 6, 2023
33b4b87
Merge pull request #18338 from apache/master
Ovilia Mar 7, 2023
5b74a22
fix: `sunbrust` label abnormal
susiwen8 Mar 7, 2023
1e6f6a9
Merge pull request #18341 from susiwen8/fix-sunbrust-book
Ovilia Mar 8, 2023
0be0cfc
feat(sankey): support `trajectory` for emphasis state #17451
ElayGelbart Mar 9, 2023
cfb3a8a
chore: release v5.4.2 (#18374)
wf123537200 Mar 14, 2023
5f49fbb
fix(i18n): fix the abbr of "March" for the DE language ("Mar" -> "Mrz…
stephanbehm Mar 15, 2023
b84493a
fix(custom): add info in custom renderItem #15789
sobolewsk Mar 23, 2023
fdda025
fix(sankey): provide missing label value in formatter #18212
TommysLee Mar 23, 2023
c89565a
Merge remote-tracking branch 'origin/release' into fix/merge-release-…
wf123537200 Mar 23, 2023
e450ae0
Merge pull request #18414 from apache/fix/merge-release-to-master
plainheart Mar 23, 2023
99e0c4e
chore: update KEYS
plainheart Mar 23, 2023
ebe5a4e
chore: update deprecated npm `prepublish` hook to `prepare`
plainheart Mar 23, 2023
3e9bd24
Merge pull request #18415 from apache/update-keys
Ovilia Mar 24, 2023
59180fd
Merge pull request #18416 from apache/update-script
Ovilia Mar 24, 2023
bb9d488
fix(src/chart/parall): fix datatype. close #18411
manishdait Mar 27, 2023
f27b615
Merge pull request #18425 from ManishDait/fix-18411
plainheart Mar 27, 2023
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .npmignore
Original file line number Diff line number Diff line change
Expand Up @@ -10,5 +10,7 @@
.DS_Store
Thumbs.db
Desktop.ini
/asset/contributing-inspect.png
CONTRIBUTING.md
# Hidden files
.*
.*
24 changes: 12 additions & 12 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,9 @@ Please check out the [Apache Code of Conduct](https://www.apache.org/foundation/

Contributions can be made in varied ways:

- Help others in the issues
- Help others with the issues
- Help solve problems with the issues
- Remind the authors to provide a demo if they are reporting for a bug
- Remind the authors to provide a demo if they are reporting a bug
- Try to reproduce the problem as described in the issues
- Make pull requests to fix bugs or implement new features
- Improve or translate the documents
Expand All @@ -19,22 +19,22 @@ Contributions can be made in varied ways:

## Issues

We have already prepared issue templates for bug report and feature request. If you want to fire an issue, just entering [New issue](https://github.com/apache/echarts/issues/new/choose) page and select either of them to get started.
We have already prepared issue templates for bug reports and feature requests. If you want to fire an issue, just enter the [New issue](https://github.com/apache/echarts/issues/new/choose) page and select either of them to get started.

Additionally, before doing so, please search for similar questions in our [issues list](https://github.com/apache/echarts/issues?utf8=%E2%9C%93&q=is%3Aissue). If you are able to reproduce an issue found in a closed issue, please create a new issue and reference the closed one.

Please read the [documentation](http://echarts.apache.org/option.html) carefully before asking any questions.

Any questions in the form of *how can I use echarts to* or *how to use echarts x feature to* belong in [Stack Overflow](http://stackoverflow.com), issues with questions like that in the issue tracker will be closed.
Any questions in the form of *how can I use echarts to* or *how to use echarts x feature to* belong in [Stack Overflow](http://stackoverflow.com). Issues with questions like that in the issue tracker will be closed.

## Release Milestone Discussion

We will start the discussion about the bugs to fix and the features of each release in the [mailing list](https://echarts.apache.org/en/maillist.html). You may subscribe to our [mailing list](https://echarts.apache.org/en/maillist.html) to give your valuable advice in milestone discussions.

Regarding the release plan, we will release a minor version at the end of every month. Here is some detail.

1. Assume our current stable release is 4.3.0. We will start the discussion of the milestone of the release two versions ahead, which is 4.5.0 at the beginning of each month. At this time we should also kickoff the development of the next release, which is 4.4.0.
2. Finish 4.4.0 developing at about 22th of this month and start the testing. And the 4.5.0 milestone discussion is frozen and published on the [GitHub](https://github.com/apache/echarts/milestone/14)
1. Assume our current stable release is 4.3.0. We will start the discussion of the milestone of the release two versions ahead, which is 4.5.0 at the beginning of each month. At this time, we should also kick off the development of the next release, which is 4.4.0.
2. Finish 4.4.0 development on about the 22nd of this month and start the testing. And the 4.5.0 milestone discussion is frozen and published on the [GitHub](https://github.com/apache/echarts/milestone/14)
3. Vote in the mailing list for the 4.4.0 release at the end of this month.

## Pull Requests
Expand All @@ -47,23 +47,23 @@ Wiki: [How to setup the dev environment](https://github.com/apache/echarts/wiki/

## Some hints about using code from other authors

+ About using some algorithms/formulas or inspired by other's work:
+ We can be inspired by other people’s work. There is no problem with copying ideas and no problems associated with that so long as the code is entirely yours and you aren’t violating the license of the inspirational work. You can just follow "normal" source code rules.
+ About using some algorithms/formulas or inspired by others' work:
+ We can be inspired by other people’s work. There is no problem with copying ideas and no problems associated with that as long as the code is entirely yours and you aren’t violating the license of the inspirational work. You can just follow "normal" source code rules.
+ But when you copy the code, even parts of files, it must remain under the copyright of the original authors.
+ What's the right thing to do for the public good here? I'll go with:
+ Be transparent when implementing an existing idea/algorithm.
+ Reference where that idea/algorithm came from.
+ Use standard language when doing so (we need to define standard language).
+ "inspired by", "learned from" and "references to" are vague concepts in copyright.
+ If any copyrightable expression is copied from the existing idea/algorithm, compare its licensing to our licensing policies and include licensing accordingly.
+ Check the original discussion about it in: https://lists.apache.org/list.html?legal-discuss@apache.org:lte=36M:echarts
+ Check the original discussion about it at: https://lists.apache.org/list.html?legal-discuss@apache.org:lte=36M:echarts
+ About adding the license/header of 3rd-party work:
+ https://www.apache.org/legal/src-headers.html#3party
+ Licenses that are compatible with the Apache license:
+ BSD and MIT are compatible with the Apache license but CC_BY_SA is not (https://apache.org/legal/resolved.html#cc-sa).
+ BSD and MIT are compatible with the Apache license, but CC_BY_SA is not (https://apache.org/legal/resolved.html#cc-sa).
+ Stack Overflow:
+ before intending to copy code from Stack Overflow, we must check:
+ before intending to copy code from Stack Overflow, we must check the following:
+ https://apache.org/legal/resolved.html#stackoverflow
+ https://issues.apache.org/jira/browse/LEGAL-471
+ Wikipedia (and most Wikimedia Foundation projects):
+ Wikipedia, and most Wikimedia Foundation projects, are licensed under CC 4.0 BY_SA (and sometimes GFDL) and is incompatible with the Apache license. Therefore, we should not copy code from Wikipedia, or Wikimedia Foundation projects.
+ Wikipedia, and most Wikimedia Foundation projects, are licensed under CC 4.0 BY_SA (and sometimes GFDL) and are incompatible with the Apache license. Therefore, we should not copy code from Wikipedia or Wikimedia Foundation projects.
49 changes: 49 additions & 0 deletions KEYS
Original file line number Diff line number Diff line change
Expand Up @@ -310,3 +310,52 @@ oEg8NMD8Wao5YN22JG30anrmYadZaghIwBz6rEuHmbf5MwcKoK349LptfHV4fhuq
5B5E6LlMNPTCWmPzYtTm5qZK
=bbcU
-----END PGP PUBLIC KEY BLOCK-----
pub ed25519 2022-12-01 [SC] [expires: 2024-11-30]
016736F5612A13D1FD04AA45CC593BC1F4F4EB7A
uid [ultimate] susiwen <susiwen8@gmail.com>
sig 3 CC593BC1F4F4EB7A 2022-12-01 susiwen <susiwen8@gmail.com>
sub cv25519 2022-12-01 [E] [expires: 2024-11-30]
sig CC593BC1F4F4EB7A 2022-12-01 susiwen <susiwen8@gmail.com>

-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEY4jDBhYJKwYBBAHaRw8BAQdAlpaQNA7ARfkPVj6EoYARkkGPdLgOmulCwScl
xGk3+8m0HHN1c2l3ZW4gPHN1c2l3ZW44QGdtYWlsLmNvbT6ImQQTFgoAQRYhBAFn
NvVhKhPR/QSqRcxZO8H09Ot6BQJjiMMGAhsDBQkDwmcABQsJCAcCAiICBhUKCQgL
AgQWAgMBAh4HAheAAAoJEMxZO8H09Ot6gcoBANBsCrZOwZtWCCQB2A6cy0or7q4c
GdyMJbP7zT5tdAAuAQDI7dy5/KE5tklZmEHJZevQLWezs6yKi+31QxcNFh6FA7g4
BGOIwwYSCisGAQQBl1UBBQEBB0A4z0jb/PpPRt/zILSBzl8XidMvvQAksexms4P4
D74EcQMBCAeIfgQYFgoAJhYhBAFnNvVhKhPR/QSqRcxZO8H09Ot6BQJjiMMGAhsM
BQkDwmcAAAoJEMxZO8H09Ot6hEABALEBaZSNzmx17PbubyiyvtaEISuzsv23RYwh
4NRHP4BkAP475WSjwMns2hSairvPXULqAcqQnjytov7CU1hbMLvgDpgzBGOMr5EW
CSsGAQQB2kcPAQEHQF85ZZTr9NstXxkToCrkVYwNuahidgRyv6S3zo2xTc6ZtC9z
dXNpd2VuIChDT0RFIFNJR05JTkcgS0VZKSA8c3VzaXdlbjhAZ21haWwuY29tPoiT
BBMWCgA7FiEEhBIjSy5LUgkGNSGQJZ0/SMJTSzwFAmOMr5ECGwMFCwkIBwICIgIG
FQoJCAsCBBYCAwECHgcCF4AACgkQJZ0/SMJTSzyNaAD+P35MI4r5nUDDg97QKYNY
m99MtUxTmcK/KGsrxYEZEDEA/jECGFvy/5WAhIRUTl4ExVsY3eBL/K2DaoTseW4a
eVEPuDgEY4yvkRIKKwYBBAGXVQEFAQEHQKNPmeMoqbHBVs5xn0c+Tz/bPW0rDDbw
Gt1pqdBMdmUvAwEIB4h4BBgWCgAgFiEEhBIjSy5LUgkGNSGQJZ0/SMJTSzwFAmOM
r5ECGwwACgkQJZ0/SMJTSzxTzQD+MTFHjt7z78fdTqbbRA6isxPV84cAFQsX4cRx
PRobcbkBAIwAkq+ddEycxZTdzaELpE08h/BLcScqbOl/ME1PTZ0H
=3Tm4
-----END PGP PUBLIC KEY BLOCK-----
pub ed25519 2023-03-15 [SC] [有效至:2025-03-14]
9C8B166777DB15AD1CC0FFBF715559B9217D4E5A
uid [ 绝对 ] zakwu <123537200@qq.com>
sig 3 715559B9217D4E5A 2023-03-15 zakwu <123537200@qq.com>
sub cv25519 2023-03-15 [E] [有效至:2025-03-14]
sig 715559B9217D4E5A 2023-03-15 zakwu <123537200@qq.com>

-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEZBE+JRYJKwYBBAHaRw8BAQdA4US4FlrxvH2Ckj5NzIkeL5nd4NyDBrlpyERo
KvlXn/C0GHpha3d1IDwxMjM1MzcyMDBAcXEuY29tPoiZBBMWCgBBFiEEnIsWZ3fb
Fa0cwP+/cVVZuSF9TloFAmQRPiUCGwMFCQPCZwAFCwkIBwICIgIGFQoJCAsCBBYC
AwECHgcCF4AACgkQcVVZuSF9TloeGAD/RjarHn34jh1NtJGi6Z8wv/XWESxyNH6g
orBPlQ+yluEBAIinhY8j/XczJQUcj9cqpMB4m8R+/jEadbaBe9pQ3uAHuDgEZBE+
JRIKKwYBBAGXVQEFAQEHQPa8rnpAhbsWw0VsCbYo1J+VeZXT/piqPpdducN3Wyh2
AwEIB4h+BBgWCgAmFiEEnIsWZ3fbFa0cwP+/cVVZuSF9TloFAmQRPiUCGwwFCQPC
ZwAACgkQcVVZuSF9Tlrc4QD/ZDd7OjcT9ShdARjcGoQ0jt6rEqL6n10V6caG+77a
89wA/R+29UlbOXNAxcQHxph8WXUZhACDhKyNETgRsgHysZQJ
=/6bg
-----END PGP PUBLIC KEY BLOCK-----
2 changes: 1 addition & 1 deletion NOTICE
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
Apache ECharts
Copyright 2017-2022 The Apache Software Foundation
Copyright 2017-2023 The Apache Software Foundation

This product includes software developed at
The Apache Software Foundation (https://www.apache.org/).
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
<img style="vertical-align: top;" src="./asset/logo.png?raw=true" alt="logo" height="50px">
</a>

Apache ECharts is a free, powerful charting and visualization library offering an easy way of adding intuitive, interactive, and highly customizable charts to your commercial products. It is written in pure JavaScript and based on <a href="https://github.com/ecomfe/zrender">zrender</a>, which is a whole new lightweight canvas library.
Apache ECharts is a free, powerful charting and visualization library offering easy ways to add intuitive, interactive, and highly customizable charts to your commercial products. It is written in pure JavaScript and based on <a href="https://github.com/ecomfe/zrender">zrender</a>, which is a whole new lightweight canvas library.

**[中文官网](https://echarts.apache.org/zh/index.html)** | **[ENGLISH HOMEPAGE](https://echarts.apache.org/en/index.html)**

Expand Down Expand Up @@ -45,12 +45,12 @@ Execute the instructions in the root directory of the echarts:
npm install

# Rebuild source code immediately in watch mode when changing the source code.
# It opens the `./test` directory and you may open `-cases.html` to get the list
# It opens the `./test` directory, and you may open `-cases.html` to get the list
# of all test cases.
# If you wish to create a test case, run `npm run mktest:help` to learn more.
npm run dev

# Check correctness of TypeScript code.
# Check the correctness of TypeScript code.
npm run checktype

# If intending to build and get all types of the "production" files:
Expand All @@ -61,7 +61,7 @@ Then the "production" files are generated in the `dist` directory.

## Contribution

If you wish to debug locally or make pull requests, please refer to the [contributing](https://github.com/apache/echarts/blob/master/CONTRIBUTING.md) document.
Please refer to the [contributing](https://github.com/apache/echarts/blob/master/CONTRIBUTING.md) document if you wish to debug locally or make pull requests.

## Resources

Expand Down
Loading