Exclude heading row when limiting imported rows #4217
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please take note of our contributing guidelines: https://docs.laravel-excel.com/3.1/getting-started/contributing.html
Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
1️⃣ Why should it be added? What are the benefits of this change?
This fixes #3439, which occurred because the heading row is included in
LimitFilter
by setting 1 as the starting row, which is the heading row when theWithHeadingRow
concern is used.2️⃣ Does it contain multiple, unrelated changes? Please separate the PRs out.
No. The PR only contains 1 commit.
3️⃣ Does it include tests, if possible?
Yes.
4️⃣ Any drawbacks? Possible breaking changes?
Some projects might rely on the current behavior. For example, they might add 1 to their desired limit and ignore the empty row. With this PR, that row could now have data which shouldn't be imported.
5️⃣ Mark the following tasks as done:
6️⃣ Thanks for contributing! 🙌