michaelbromley / michaelbromley/angularUtils

dirPagination: accessing visible repeated items

Open
#437 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2k
Forks
842
PR merge metrics
No merged PRs in 30d

Description

Hey Michael --

First thanks for all the work you've put into this.

I'm using dirPagination on a table with repeated rows and i'm trying to implement a method that will select the rows that are on the current page rather than ALL of the rows. Is there an out of the box way to select ONLY the current page's rows when using the 'select all' checkbox' ?

Here's a plunkr with the select all method hitting all rows across pages.
http://plnkr.co/edit/ZwzCzhc1vUgOS4gHZjzd?p=preview

Is there a subset of the $scope.collection that I can access?

This [StackOverflow](http://stackoverflow.com/questions/31191473/angularjs-dirpagination-select-all-visible-rows) question gets at the behavior I'm looking for, but the solution seems very hacky.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Plunkr and the dirPagination behavior described in the issue, then compare it with the linked StackOverflow question. Determine whether the component exposes a subset representing only the visible page. Done means the select-all action affects rows on the current page without requiring the described hack.

Written by the indexing model from the issue text.

Assessment

Tech stack
angularjs, javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.