When receiving a drop, I want to add server side drop criteria, because I have complex calculations on server side for accepting the drop
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Will require UX testing on what to show to the user while client side is waiting for the server side acceptance criteria.
The server side call might need to be delayed until the user has "stopped" at some drop target.
One option would be to show a "maybe" drop hint for the user before the server side criteria has been resolved.
The API itself should be really simple: just provide the data from the drag/dragenter event and return whether the drop is acceptable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the existing drag, dragenter, and drop handling and how drop-target feedback is presented. Define the UX for waiting or showing a “maybe” hint, then verify that the server-side API can receive drag-event data and return an acceptance decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100