Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

vue-sliding-pagination

Package Overview
Dependencies
Maintainers
1
Versions
20
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

vue-sliding-pagination

Sliding pagination component

  • 1.0.0-beta-5
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
718
increased by24.65%
Maintainers
1
Weekly downloads
 
Created
Source

[TODO:] [Insert] [a crapton] [of badges] [here] [because] [javascript]

Build Status

Sliding Pagination for Vue

ARIA-friendly pagination component with a sliding window.

Example pagination

Disclaimer: This package is currently still in beta and not recommended for production use yet.

Installation

Node

npm install vue-sliding-pagination --save

or, for the fäncÿ people,

yarn add vue-sliding-pagination

Browser

Currently, no browser build is available.

Usage

Basic usage of the pagination component only requires the current page, the total number of pages and a handler which is called on page change.

The pagination component does not handle page changes by itself, instead you are required to provide a page change handler which should contain all your page changing logic (e.g. a vuex store dispatch) and eventually change the current page to the passed one. In later releases, a v-model approach to currentPage may be offered, but was opted against for the time being.

Thus, to get a paginator with default settings (please consult the options listing below for details), the following markup and script sections provide a starting point:

<sliding-pagination
  :current="currentPage"
  :total="totalPages"
  @page-change="pageChangeHandler"
></sliding-pagination>
import SlidingPagination from 'vue-sliding-pagination'

// in component or vue instance
components: {
  // ...
  SlidingPagination
},
data() {
  return {
    // ...
    currentPage: 1,
    totalPages: 10
  }
},
methods: {
  // ...
  pageChangeHandler(selectedPage) {
    this.currentPage = selectedPage
  }
}

Options

nametypedefaultdescription
ariaPaginationLabelString'Pagination navigation'ARIA label for the whole area
ariaGotoPageLabelString'Go to page %page% of %total%'ARIA label for a page link that is not the current page
ariaPreviousPageLabelString'Go to previous page'ARIA label for the previous page action
ariaNextPageLabelString'Go to next page'ARIA label for the next page action
ariaCurrentPageLabelString'Page %current of %total, current page'ARIA label for the current page
currentNumber-Integer representing the current page
totalNumber-Integer representing the total number of pages
slidingEndingSizeNumber2Number of always listed pages on the beginning and end
slidingWindowSizeNumber3Number of pages in the sliding window
nonSlidingSizeNumber9Number of pages before the paginator switches to sliding mode
pageComponentString'sliding-pagination-default-page'Component name (must be registered) for the page elements

Customization

The component offers severals customization options.

ARIA labels

All ARIA labels can be altered and localized.

The labels ariaGoToPageLabel and ariaCurrentPageLabel support the following template variables:

VariableTypeDescription
%total%NumberThe total number of pages
%page%NumberThe page under the cursor

Intervals

The number of pages shown on the beginning and ending of the pager as well as the number of pages in the pagination window can be changed dynamically. The break-point from normal to sliding-window pagination can also be adjusted. Please bear in mind that none of these intervals and none of the calculations they are used in make any assertions on obviously impossible configurations!

What are obviously impossible configurations?

Glad you're asking! For one, the rule of thumb should be 2 * slidingEndingSize + slidingWindowSize <= total. However, as there is a fallback coated as nonSlidingSize you can work around this "limitation" with some ingenouity on your part. Basically, don't do stupid things that disregards principles of natural numbers.

Page navigation

The content of the previous and next page elements are customizable via the slots previous-page and next-page. By default, these only contain the "pretend arrows" aka « and ». The contents of these slots are only intended for visual use. Screenreader users are presented the ariaPreviousPageLabel and ariaNextPageLabel instead.

Gaps

Depending on the current page, there may be a gap between the sliding window and the beginning and ending pages. The gap content defaults to … but can be customized for visual use under the same conditions as the page navigation with the slots gap-left and gap-right.

Page component

Since actual pages are the most active element of the whole pagination deal, they have been implemented with the <component :is="paginationComponent"> pattern.

The SlidingPaginationDefaultPage component offers guidance into how a basic component representing page elements should look like. It's unit test can be used as a basis for unit testing custom page components.

The page component receives the following props:

nametypedescription
ariaPageLabelStringThe computed ARIA page label
isCurrentBooleanIs the page the current page
pageNumberThe page number to display

It is by no means required to implement all properties of the default page. A custom pagination component can usually just be implemented as render function, e.g.

Vue.component('ExamplePageComponent', {
  props: {
    page: {
      type: Number,
      required: true
    }
  },

  render (h) {
    return h('a', { class: 'page-component' }, this.page)
  }
})
<sliding-pagination
  ...
  pagination-component="example-page-component"
></sliding-pagination>

Please keep in mind that the above example is absurdly simple for demonstration purposes and breaks the ARIA compatibility of the whole pagination component.

Styling

The CSS classes used in the component are following the BEM-Methodology, regarding only the component itself as a block and going downward from there, thus the corresponding classes to interface elements are:

ClassInterface element
.c-sliding-paginationThe whole component i.e. the <nav> container
.c-sliding-pagination__listThe <ul> containing all navigational and page elements
.c-sliding-pagination__list-elementEach <li> representing either a navigational or a page element
.c-sliding-pagination__list-element--activeThe <li> representing the current page
.c-sliding-pagination__list-element--disabledDisabled navigational elements
.c-sliding-pagination__pageThe page element inside an <li> (typically an <a>)

For ease of customization, the original SCSS styling files are available in the distribution package in the dist/styles subdir.

Contributing

Please do. Please be kind to each other. That's all.

License

Copyright 2018 Stefan "eFrane" Graupner

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Keywords

FAQs

Package last updated on 12 Dec 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc