Skip to content

Commit 55714f6

Browse files
veghdevveghdev
committed
Version number increased to 0.7.2
1 parent 63637a1 commit 55714f6

File tree

8 files changed

+172
-83
lines changed

8 files changed

+172
-83
lines changed

‎CHANGELOG.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,7 @@
22

33
## [Unreleased]
44

5-
### Added
6-
7-
- New 'direction' anim option introduced.
5+
## [0.7.2] - 2023-05-09
86

97
### Fixed
108

@@ -13,6 +11,10 @@
1311
- If dimension data series re-added, previously existed categories and order
1412
will remains.
1513

14+
### Added
15+
16+
- New 'direction' anim option introduced.
17+
1618
## [0.7.1] - 2023-02-24
1719

1820
### Fixed

‎CODE_OF_CONDUCT.md

Lines changed: 110 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -1,72 +1,132 @@
11
# Code of Conduct
22

3-
Our community welcomes participants from around the world with different experiences, unique perspectives, and great ideas to share.
3+
Our community welcomes participants from around the world with different
4+
experiences, unique perspectives, and great ideas to share.
45

5-
Whenever we come together as a community, we are here to support each other, to learn from each other’s successes, and to encourage our members to become the Vizzu users they visualize.
6+
Whenever we come together as a community, we are here to support each other, to
7+
learn from each other’s successes, and to encourage our members to become the
8+
Vizzu users they visualize.
69

7-
As a member of the Vizzu community, you accept to follow the below Code of Conduct.
10+
As a member of the Vizzu community, you accept to follow the below Code of
11+
Conduct.
812

913
## Our Pledge
10-
In the interest of fostering an open and welcoming environment, we as members, users, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual
11-
identity and orientation.
14+
15+
In the interest of fostering an open and welcoming environment, we as members,
16+
users, contributors, and leaders pledge to make participation in our community a
17+
harassment-free experience for everyone, regardless of age, body size, visible
18+
or invisible disability, ethnicity, sex characteristics, gender identity and
19+
expression, level of experience, education, socio-economic status, nationality,
20+
personal appearance, race, caste, color, religion, or sexual identity and
21+
orientation.
1222

1323
## Our Standards
14-
Examples of behavior that contributes to a positive environment for our community include:
15-
16-
* Using welcoming and inclusive language?
17-
* Showing empathy and kindness toward other people
18-
* Being respectful of differing opinions, viewpoints, and experiences
19-
* Giving and gracefully accepting constructive feedback
20-
* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
21-
* Attempting collaboration before conflict
22-
* Sharing your knowledge and ask questions
23-
* Giving credit when the credit is deserved
24-
* Focusing on what is best for the community
24+
25+
Examples of behavior that contributes to a positive environment for our
26+
community include:
27+
28+
- Using welcoming and inclusive language?
29+
- Showing empathy and kindness toward other people
30+
- Being respectful of differing opinions, viewpoints, and experiences
31+
- Giving and gracefully accepting constructive feedback
32+
- Accepting responsibility and apologizing to those affected by our mistakes,
33+
and learning from the experience
34+
- Attempting collaboration before conflict
35+
- Sharing your knowledge and ask questions
36+
- Giving credit when the credit is deserved
37+
- Focusing on what is best for the community
2538

2639
Examples of unacceptable behavior include:
2740

28-
* Violence, threats of violence, or inciting others to commit self-harm
29-
* The use of sexualized language or imagery and unwelcome sexual attention or advances
30-
* Trolling, intentionally spreading misinformation, insulting/derogatory comments, and personal or political attacks
31-
* Public or private harassment
32-
* Publishing others' private information, such as a physical or electronic address, without explicit permission
33-
* Represent someone else’s work or words as your own
34-
* Abuse of the reporting process to intentionally harass or exclude others
35-
* Advocating for, or encouraging, any of the above behavior
36-
* Other conduct which could reasonably be considered inappropriate in a professional setting
41+
- Violence, threats of violence, or inciting others to commit self-harm
42+
- The use of sexualized language or imagery and unwelcome sexual attention or
43+
advances
44+
- Trolling, intentionally spreading misinformation, insulting/derogatory
45+
comments, and personal or political attacks
46+
- Public or private harassment
47+
- Publishing others' private information, such as a physical or electronic
48+
address, without explicit permission
49+
- Represent someone else’s work or words as your own
50+
- Abuse of the reporting process to intentionally harass or exclude others
51+
- Advocating for, or encouraging, any of the above behavior
52+
- Other conduct which could reasonably be considered inappropriate in a
53+
professional setting
3754

3855
## Enforcement Responsibilities
39-
Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action and will communicate reasons for moderation decisions when appropriate.
4056

41-
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 a user or contributor in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
57+
Project maintainers are responsible for clarifying and enforcing our standards
58+
of acceptable behavior and will take appropriate and fair corrective action and
59+
will communicate reasons for moderation decisions when appropriate.
60+
61+
Project maintainers have the right and responsibility to remove, edit, or reject
62+
comments, commits, code, wiki edits, issues, and other contributions that are
63+
not aligned to this Code of Conduct, or to ban temporarily or permanently a user
64+
or contributor in response to any behavior that they deem inappropriate,
65+
threatening, offensive, or harmful.
4266

4367
## Scope
44-
This Code of Conduct applies both within community spaces and in public spaces when an individual is representing this community or the project.
4568

46-
Examples of representing our community include using an official 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.
69+
This Code of Conduct applies both within community spaces and in public spaces
70+
when an individual is representing this community or the project.
71+
72+
Examples of representing our community include using an official e-mail address,
73+
posting via an official social media account, or acting as an appointed
74+
representative at an online or offline event. Representation of a project may be
75+
further defined and clarified by project maintainers.
4776

4877
## Enforcement
49-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to us anonymously through [this form](https://share.hsforms.com/1IRUYnCo3QPa1ZiYDV4oYGgc5lac). All complaints will be reviewed and investigated promptly and fairly. All project maintainers are obligated to respect the privacy and security of the reporter of any incident.
50-
51-
Project maintainers will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
52-
1. Correction
53-
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
54-
Consequence: A private, written warning from Project maintainers, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
55-
2. Warning
56-
Community Impact: A violation through a single incident or series of actions.
57-
Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
58-
3. Temporary Ban
59-
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
60-
Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
61-
4. Permanent Ban
62-
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
63-
Consequence: A permanent ban from any sort of public interaction within the community.
64-
65-
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.
66-
67-
If you are unsure whether an incident is a violation, or whether the space where the incident took place is covered by our Code of Conduct, we encourage you to still report it. We would prefer to have a few extra reports where we decide to take no action than to leave an incident go unnoticed and unresolved that may result in an individual or group to feel like they can no longer participate in the community. Reports deemed as not a violation will also allow us to improve our Code of Conduct and processes surrounding it. If you witness a dangerous situation or someone in distress, we encourage you to report even if you are only an observer.
6878

69-
## Attribution
70-
This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
79+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
80+
reported to us anonymously through
81+
[this form](https://share.hsforms.com/1IRUYnCo3QPa1ZiYDV4oYGgc5lac). All
82+
complaints will be reviewed and investigated promptly and fairly. All project
83+
maintainers are obligated to respect the privacy and security of the reporter of
84+
any incident.
85+
86+
Project maintainers will follow these Community Impact Guidelines in determining
87+
the consequences for any action they deem in violation of this Code of Conduct:
88+
89+
- Correction Community Impact: Use of inappropriate language or other behavior
90+
deemed unprofessional or unwelcome in the community. Consequence: A private,
91+
written warning from Project maintainers, providing clarity around the nature
92+
of the violation and an explanation of why the behavior was inappropriate. A
93+
public apology may be requested.
94+
- Warning Community Impact: A violation through a single incident or series of
95+
actions. Consequence: A warning with consequences for continued behavior. No
96+
interaction with the people involved, including unsolicited interaction with
97+
those enforcing the Code of Conduct, for a specified period of time. This
98+
includes avoiding interactions in community spaces as well as external
99+
channels like social media. Violating these terms may lead to a temporary or
100+
permanent ban.
101+
- Temporary Ban Community Impact: A serious violation of community standards,
102+
including sustained inappropriate behavior. Consequence: A temporary ban from
103+
any sort of interaction or public communication with the community for a
104+
specified period of time. No public or private interaction with the people
105+
involved, including unsolicited interaction with those enforcing the Code of
106+
Conduct, is allowed during this period. Violating these terms may lead to a
107+
permanent ban.
108+
- Permanent Ban Community Impact: Demonstrating a pattern of violation of
109+
community standards, including sustained inappropriate behavior, harassment of
110+
an individual, or aggression toward or disparagement of classes of
111+
individuals. Consequence: A permanent ban from any sort of public interaction
112+
within the community.
113+
114+
Project maintainers who do not follow or enforce the Code of Conduct in good
115+
faith may face temporary or permanent repercussions as determined by other
116+
members of the project's leadership.
117+
118+
If you are unsure whether an incident is a violation, or whether the space where
119+
the incident took place is covered by our Code of Conduct, we encourage you to
120+
still report it. We would prefer to have a few extra reports where we decide to
121+
take no action than to leave an incident go unnoticed and unresolved that may
122+
result in an individual or group to feel like they can no longer participate in
123+
the community. Reports deemed as not a violation will also allow us to improve
124+
our Code of Conduct and processes surrounding it. If you witness a dangerous
125+
situation or someone in distress, we encourage you to report even if you are
126+
only an observer.
71127

128+
## Attribution
72129

130+
This Code of Conduct is adapted from the Contributor Covenant, version 2.1,
131+
available at
132+
https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

‎CONTRIBUTING.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,3 @@
1-
See the project's [Wiki page](https://github.com/vizzuhq/vizzu-lib/wiki).
1+
# Contributing
2+
3+
See the project's [Wiki page](https://github.com/vizzuhq/vizzu-lib/wiki).

‎FAQ.md

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,26 +2,30 @@
22

33
## How to use Vizzu with Webpack, React, Vite and other bundlers/frameworks?
44

5-
Here's a tutorial and an example:
6-
7-
https://lib.vizzuhq.com/latest/tutorial/initialization/#working-with-bundlers-frameworks
5+
Here's
6+
[a tutorial and an example](https://lib.vizzuhq.com/latest/tutorial/initialization/#working-with-bundlers-frameworks).
87

98
## Why on(), off(), feature() methods fail after constructor call?
109

11-
The Vizzu constructor has to load Vizzu's WebAssembly module asynchronously to prevent blocking the whole page.
12-
Because of this, any method except `animate()` will throw an exception while the library is not initialized.
10+
The Vizzu constructor has to load Vizzu's WebAssembly module asynchronously to
11+
prevent blocking the whole page. Because of this, any method except `animate()`
12+
will throw an exception while the library is not initialized.
1313

14-
There is an `initializing` promise in the Vizzu class, which will resolve when initialization is finished. You can call all methods after
15-
this promise is resolved.
14+
There is an `initializing` promise in the Vizzu class, which will resolve when
15+
initialization is finished. You can call all methods after this promise is
16+
resolved.
1617

1718
## How to load data from CSV into Vizzu?
1819

19-
This example reads the data from a CSV: https://lib.vizzuhq.com/0.3.0/content/howtos/csv-input/
20+
This [example](https://lib.vizzuhq.com/0.3.0/content/howtos/csv-input/) reads
21+
the data from a CSV.
2022

21-
You can find the source here; the CSV loading part is in the csv-input.js file: https://github.com/vizzuhq/vizzu-lib-doc/tree/gh-pages/0.3.0/content/howtos/csv-input
23+
You can find the source
24+
[here](https://github.com/vizzuhq/vizzu-lib-doc/tree/gh-pages/0.3.0/content/howtos/csv-input);
25+
the CSV loading part is in the csv-input.js file.
2226

2327
## How to remove fraction digits on integer labels during animation?
2428

25-
The maximum number of fraction digits can be set for marker and axis labels with
29+
The maximum number of fraction digits can be set for marker and axis labels with
2630
[maxFractionDigits](https://lib.vizzuhq.com/latest/reference/interfaces/vizzu.Styles.MarkerLabel/#maxfractiondigits)
2731
style parameter.

‎PROJECTS.md

Lines changed: 27 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,34 @@
1-
This is the list of official and 3rd party projects (extensions, bindings, templates, etc)
2-
related to the Vizzu library.
1+
# Projects
2+
3+
This is the list of official and 3rd party projects (extensions, bindings,
4+
templates, etc) related to the Vizzu library.
35

46
If you know any project not listed here please feel free to edit this file and
57
send a pull request.
68

79
Official:
8-
* Bindings
9-
* [[ipyvizzu](https://github.com/vizzuhq/ipyvizzu)] **Jupyter Notebook** integration for Vizzu
10-
* Extensions
11-
* [[vizzu-ext-js-story](https://github.com/vizzuhq/vizzu-ext-js-story)] **Presentation** control extension for Vizzu data stories
12-
* [[vizzu-ext-js-scrollytelling](https://github.com/vizzuhq/vizzu-ext-js-scrollytelling)] **ScrollyTelling** extension for articles with Vizzu
13-
* Templates
14-
* [[vizzu-webpack-demo](https://github.com/vizzuhq/vizzu-webpack-demo)] Howto and example for using Vizzu with **Webpack**
15-
* [[vizzu-react-example](https://github.com/vizzuhq/vizzu-react-example)] Howto and example for using Vizzu with **React**
16-
* [[vizzu-vite-demo](https://github.com/vizzuhq/vizzu-vite-demo)] Howto and example for using Vizzu with **Vite**
17-
* [[vizzu-pyscript-example](https://github.com/vizzuhq/vizzu-pyscript-example)] Howto and example for using Vizzu in **PyScript**
10+
11+
- Bindings
12+
- \[[ipyvizzu](https://github.com/vizzuhq/ipyvizzu)\] **Jupyter Notebook**
13+
integration for Vizzu
14+
- Extensions
15+
- \[[vizzu-story-js](https://github.com/vizzuhq/vizzu-story-js)\]
16+
**Presentation** control extension for Vizzu data stories
17+
- \[[vizzu-ext-js-scrollytelling](https://github.com/vizzuhq/vizzu-ext-js-scrollytelling)\]
18+
**ScrollyTelling** extension for articles with Vizzu
19+
- Templates
20+
- \[[vizzu-webpack-demo](https://github.com/vizzuhq/vizzu-webpack-demo)\]
21+
Howto and example for using Vizzu with **Webpack**
22+
- \[[vizzu-react-example](https://github.com/vizzuhq/vizzu-react-example)\]
23+
Howto and example for using Vizzu with **React**
24+
- \[[vizzu-vite-demo](https://github.com/vizzuhq/vizzu-vite-demo)\] Howto and
25+
example for using Vizzu with **Vite**
26+
- \[[vizzu-pyscript-example](https://github.com/vizzuhq/vizzu-pyscript-example)\]
27+
Howto and example for using Vizzu in **PyScript**
1828

1929
Unofficial:
20-
* [[christopher-caldwell/vizzu-vite-demo](https://github.com/christopher-caldwell/vizzu-vite-demo)] Starter template on running Vizzu with **Vite**
21-
* [[triptych/hello-vizzu](https://observablehq.com/@triptych/hello-vizzu)] **Observable** Vizzu example
30+
31+
- \[[christopher-caldwell/vizzu-vite-demo](https://github.com/christopher-caldwell/vizzu-vite-demo)\]
32+
Starter template on running Vizzu with **Vite**
33+
- \[[triptych/hello-vizzu](https://observablehq.com/@triptych/hello-vizzu)\]
34+
**Observable** Vizzu example

‎README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -117,12 +117,12 @@ chart.animate({
117117
## FAQ
118118

119119
You can find answers to the most frequently asked questions about using the
120-
library in our [FAQ](https://github.com/vizzuhq/vizzu-lib/blob/main/FAQ.md).
120+
library in our [FAQ](https://lib.vizzuhq.com/latest/FAQ/).
121121

122122
## Projects
123123

124124
List of external projects (extensions, bindings, templates, etc) for Vizzu:
125-
[Projects](https://github.com/vizzuhq/vizzu-lib/blob/main/PROJECTS.md).
125+
[Projects](https://lib.vizzuhq.com/latest/PROJECTS/).
126126

127127
## Roadmap
128128

‎src/chart/main/version.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
#include "version.h"
22

3-
const App::Version Vizzu::Main::version(0, 7, 1);
3+
const App::Version Vizzu::Main::version(0, 7, 2);
44

55
const char *Vizzu::Main::siteUrl = "https://vizzuhq.com/";

‎tools/docs-check/Makefile

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,11 @@ format: $(DEV_BUILD_FLAG) $(DEV_JS_BUILD_FLAG)
6565
--end-of-line keep \
6666
--line-length 70 \
6767
../../docs \
68-
../../README.md
68+
../../README.md \
69+
../../CODE_OF_CONDUCT.md \
70+
../../CONTRIBUTING.md \
71+
../../FAQ.md \
72+
../../PROJECTS.md
6973
npm run prettier
7074

7175
check-format: $(DEV_BUILD_FLAG) $(DEV_JS_BUILD_FLAG)
@@ -75,7 +79,11 @@ check-format: $(DEV_BUILD_FLAG) $(DEV_JS_BUILD_FLAG)
7579
--end-of-line keep \
7680
--line-length 70 \
7781
../../docs \
78-
../../README.md
82+
../../README.md \
83+
../../CODE_OF_CONDUCT.md \
84+
../../CONTRIBUTING.md \
85+
../../FAQ.md \
86+
../../PROJECTS.md
7987
npm run check-prettier
8088

8189
lint: $(DEV_BUILD_FLAG) $(DEV_JS_BUILD_FLAG)

0 commit comments

Comments
 (0)