felixrieseberg / felixrieseberg/React-Dropzone-Component

No sequential deletion

Open
#131 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
999
Forks
148
PR merge metrics
No merged PRs in 30d

Description

No sequential deletion ,you didn't add i in ForEach, i is always undefined.
![2017-06-19 1 10 45](https://user-images.githubusercontent.com/13556731/27270444-c0873518-54f0-11e7-9e70-695c6a6483a5.png)

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 by reproducing the reported non-sequential deletion behavior in the file-deletion flow and inspect the ForEach usage highlighted by the issue. Confirm that deletion proceeds in sequence and verify the behavior with the project's existing tests, if available.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.