Skip to content

Improve custom pagination view documentation #4824

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Improve custom pagination view documentation #4824

wants to merge 1 commit into from

Conversation

guizoxxv
Copy link
Contributor

@guizoxxv guizoxxv commented Dec 11, 2018

At first I didn't understood that the view part of the parameter is the name of the file inside resources/views/vendor/pagination.

@taylorotwell
Copy link
Member

I think it's simpler to just change the view names. We really shouldn't put views in that vendor folder. I'll fix it.

@guizoxxv guizoxxv deleted the patch-3 branch April 6, 2019 01:30
taylorotwell pushed a commit that referenced this pull request Nov 30, 2021
If the callback given to `skipWhile` never returns `false`, then an
empty collection would be returned. Currently the documentation states
the opposite. If the callback never returns `true`, then the whole
collection is returned unfiltered.

```
>>> $collection = collect([1, 2, 3, 4]);
=> Illuminate\Support\Collection {#4833
     all: [
       1,
       2,
       3,
       4,
     ],
   }
>>> $subset = $collection->skipWhile(function ($item) { return false; });
=> Illuminate\Support\Collection {#4835
     all: [
       1,
       2,
       3,
       4,
     ],
   }
>>> $subset = $collection->skipWhile(function ($item) { return true; });
=> Illuminate\Support\Collection {#4824
     all: [],
   }
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants