@epic-startinn/vue-pivottable v0.10.1

Vue Pivottable

It is a Vue port of the jQuery-based PivotTable.js

Documentation

Documentation is still under development, but you can view it at https://seungwoo321.github.io/vue-pivottable.

Live Demo

link

Example Code

# Clone the project
git clone https://github.com/Seungwoo321/vue-pivottable.git

# Go into the cloned directory
cd vue-pivottable/demo/example-vue-cli3/

# npm install
npm install

# npm run serve
npm run serve

Open browser to http://localhost:8080

Installation

npm i vue-pivottable

Usage

• Vue Pivottable

<template>
  <vue-pivottable
    :data="[{color: 'blue', shape: 'circle'},{color: 'red', shape: 'triangle'}]"
    :rows="['color']"
    :cols="['shape']"
  >
  </vue-pivottable>
</template>

<script>
import { VuePivottable } from 'vue-pivottable'
import 'vue-pivottable/dist/vue-pivottable.css'
export default {
  components: {
    VuePivottable
  }
}
</script>

• Vue Pivottable Ui

<template>
  <vue-pivottable-ui
    :data="[{color: 'blue', shape: 'circle'},{color: 'red', shape: 'triangle'}]"
    :rows="['color']"
    :cols="['shape']"
  >
  </vue-pivottable-ui>
</template>

<script>
import { VuePivottableUi } from 'vue-pivottable'
import 'vue-pivottable/dist/vue-pivottable.css'
export default {
  components: {
    VuePivottableUi
  }
}
</script>

Inspired

• plotly/react-pivottable - React-based pivot table library
• David-Desmaisons/vue-plotly - vue wrapper for plotly.js

License

MIT

Creating releases

Releases are created by GitHub with semantic-release, which checks all the commit messages since the last release to determine what the new version number should be.

Commit messages

To trigger a release, your commits need to follow the Angular Commit Message Conventions, meaning they need to be written in this pattern:

type(context): message

Type

Commits using the types feat, fix or perf will appear in the changelogs. However, any commit with BREAKING CHANGE in the body will also appear in the changelog, regardless of the type.

The type should be one of the following:

• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs)
• docs: Documentation only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that neither fixes a bug nor adds a feature
• style: Changes that do not affect the meaning of the code (white-space, formatting, adding commas, removing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

Context

For the context, we add the Jira ticket number. It's optional but good to have since the release logs are generated from the commits.

Examples

💡 To add a body to your commit message, you can use git commit -m "TITLE" -m "BODY"