Within the documentation for labels there is no mention of the available props you can change, such as :labelRotate and :labelColor without having to look into the code. I believe the documentation for labels should be updated.

Browser: Chrome

When I change the rounding prop it doesn't change anything.

My input:

   <bars
          data="[1, 2, 5, 9, 5, 10, 3, 5, 2, 5, 1, 8, 2]"
          gradient="['#00ac84']"
          :barWidth="10"
          :rounding="4"
    />

Output:

Seems ok on firefox, but when changing "padding" param on chrome I got bars with bad alignment

Labels either below or on the individual bar.

Hi!

Would you accept a prop that would flip the bars to be rendered horizontally (instead of vertically)?
All naming suggestions are also welcome (since flip might not be that obvious).

Best,
andreas

On the website: https://deviavir.github.io/vue-bar/ the bars load vertically, from bottom (0), to top of the value range (say, 12).

However in practice: https://jsfiddle.net/1bvxyjhk/ (example in README)

The bars load vertically as expected, but from top to bottom (which seems a bit more awkward).

This seems to happen in 1.5.0 but not earlier versions.

Some possible solutions:

1. Fix so bars load from bottom to top as before
2. Fix so that negative bars load from 0 to their value, and positive bars 0 to their value
3. Have option for which direction bars load vertically, and as mentioned in another issue possibility to load them horizontally

Unlike Vue-trend, vue-bar does not rebuilt its own SVG after data that's been feeding this svg has changed.

Here's my example:

<template>
  <div class="row">
    <div class="col-12">
        <button class="btn btn-future" @click="refresh">Refresh</button>

        <hr>

        <bars
          :data="bars"
          :gradient="['#6fa8dc', '#42b983']"
          :barWidth="2" :rounding="1">
        </bars>
    </div>
  </div>
</template>

<script>
  import _ from 'lodash'

  export default {
    data() {
      return {
        bars: [],
        trends: []
      }
    },

    created() {
      this.randomArray();
    },

    methods: {
      randomArray() {
        this.bars = _.times(100, _.random.bind(30, 10000));
        this.trends = _.times(100, _.random.bind(30, 10000));
      },
      refresh() {
        this.randomArray();
      }
    }
  }
</script>

Hi,
should be possibile to add negative bars?

Thank you

Would it be possible to accept a prop to change the font size? On a graph with multiple labels, the text gets cut off on the sides because it's too big.

While playing with playground I got those:

If all values are zero would expect either a blank chart OR more preferable a chart with a tiny dash for each bar

Hi!
I'm using the vue-bars module on a codepen project.
It appeared to work, however, I've encountered this error when trying to render a graph:

parameters:

<bars
       :data="numbers">
    </bars>

numbers is a data object with the following structure:

numbers: [
        { key: 1 },
        { key: 2 },
        { key: 3 },
      ]

link to codepen project

Awesome project!

How do I display a custom tooltip when I hover over a bar?

Thanks!

When I made the update for the labels, I pretty much only did enough for my own needs. However that update was not backwards compatible and will break existing implementations.

My plan is to make the x-axis labels an optional parameter passed in as an array of text. This issue will serve to also let others know I am working on this if your build breaks in the meantime, update your packages.json for version 0.1.3

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Using expressVue so unable to pass this to Vue.use. That being said not entirely sure that this shouldn't work using the import alone. Wondering if there is something in the files that could be causing conflict or if there might be a way to install this using expressVue and serverside rendering.

From

 h(Path, {

Thanks.

Hello,

Thanks for creating this simple bar chart.
Does this will work with vue 3?

In the dependencies is "vue": "^2.5.21"

 <!-- Expected showing 15 columns -->
  <bars
    :data="[1, 2, -5, 9, 5, 10, 3, 5, 5, 12, 1, 8, 2, 9, 14]"
    :gradient="['#6fa8dc', '#42b983']"
    :barWidth="5"
    :growDuration="1">
  </bars>
 <!-- it's working fine as I expected -->
  
 <!-- Expected showing 2 columns -->
  <bars
    :data="[1, 2]"
    :gradient="['#6fa8dc', '#42b983']"
    :barWidth="100"
    :growDuration="1"
  >
  </bars>
  <!-- It's not working properly as I expected -->

Attached the image below.

I believe I am explaining properly now and want to resolve this issue asap.

The last few pull requests:

• labelSize prop
• labelColor prop
• labelRotate prop
• Negative Bars feature

Did not include README changes to their pull requests to add the new features / props in the API docs.

(Adding issues so I may tackle them myself, for reference)

Related to #23

I can't set solid color in bars. it's interesting

em as a unit of measurement is a less modern "font size" unit of measurement. Many frameworks (such as the 4.0.0 bootstrap) try to use "rem" (root em) instead, which does a proportional size compared to a single root size (for use in scaling the UI of an app, usually in @media queries). Other applications might use em, or pt, or any other measurement.

I think an apt change would be to:

1. Change the default to "0.7rem". Right now, 0.7em is quite large for any app that does both mobile and desktop.
2. Allow the labelSize prop to accept a unit attached such as "12px", "12pt", "12em" (or a labelSizeUnit prop)

As with the other issue, might try and tackle this myself, making issue for reference.

Also, I'm not sure if this is a bug, but "labelSize" PR seemed to only edit files in dist/ not the files in src/ but I'm not sure if that is intentional or not.

I have an error rendering your template example.
Is it bug or I am doing something wrong on setup ?

Rotation axis seems wrongly set in the middle of the label....

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Like "statistics" here:
https://dribbble.com/shots/3528275-Dashboard-UI/attachments/782647