chartkick 3.2.0 → 3.3.2
Sign up to get free protection for your applications and to get access to all the features.
Potentially problematic release.
This version of chartkick might be problematic. Click here for more details.
- checksums.yaml +4 -4
- data/CHANGELOG.md +70 -47
- data/README.md +45 -16
- data/lib/chartkick/helper.rb +12 -10
- data/lib/chartkick/version.rb +1 -1
- data/vendor/assets/javascripts/Chart.bundle.js +4432 -2965
- data/vendor/assets/javascripts/chartkick.js +202 -30
- metadata +3 -4
- data/CONTRIBUTING.md +0 -46
data/CONTRIBUTING.md
DELETED
|
@@ -1,46 +0,0 @@
|
|
|
1
|
-
# Contributing
|
|
2
|
-
|
|
3
|
-
First, thanks for wanting to contribute. You’re awesome! :heart:
|
|
4
|
-
|
|
5
|
-
## Help
|
|
6
|
-
|
|
7
|
-
We’re not able to provide support through GitHub Issues. If you’re looking for help with your code, try posting on [Stack Overflow](https://stackoverflow.com/).
|
|
8
|
-
|
|
9
|
-
All features should be documented. If you don’t see a feature in the docs, assume it doesn’t exist.
|
|
10
|
-
|
|
11
|
-
## Bugs
|
|
12
|
-
|
|
13
|
-
Think you’ve discovered a bug?
|
|
14
|
-
|
|
15
|
-
1. Search existing issues to see if it’s been reported.
|
|
16
|
-
2. Try the `master` branch to make sure it hasn’t been fixed.
|
|
17
|
-
|
|
18
|
-
```rb
|
|
19
|
-
gem "chartkick", github: "ankane/chartkick"
|
|
20
|
-
```
|
|
21
|
-
|
|
22
|
-
If the above steps don’t help, create an issue. Include:
|
|
23
|
-
|
|
24
|
-
- Detailed steps to reproduce
|
|
25
|
-
- JavaScript rendered by Chartkick
|
|
26
|
-
- Complete backtraces for exceptions
|
|
27
|
-
|
|
28
|
-
## New Features
|
|
29
|
-
|
|
30
|
-
If you’d like to discuss a new feature, create an issue and start the title with `[Idea]`.
|
|
31
|
-
|
|
32
|
-
## Pull Requests
|
|
33
|
-
|
|
34
|
-
Fork the project and create a pull request. A few tips:
|
|
35
|
-
|
|
36
|
-
- Submit JavaScript changes to the [Chartkick.js](https://github.com/ankane/chartkick.js) repo.
|
|
37
|
-
- Keep changes to a minimum. If you have multiple features or fixes, submit multiple pull requests.
|
|
38
|
-
- Follow the existing style. The code should read like it’s written by a single person.
|
|
39
|
-
|
|
40
|
-
Feel free to open an issue to get feedback on your idea before spending too much time on it.
|
|
41
|
-
|
|
42
|
-
Also, note that we aren’t currently accepting new chart types.
|
|
43
|
-
|
|
44
|
-
---
|
|
45
|
-
|
|
46
|
-
This contributing guide is released under [CCO](https://creativecommons.org/publicdomain/zero/1.0/) (public domain). Use it for your own project without attribution.
|