nextcloud / nextcloud/deck

move card: after change of target board target could be invalid

Open
#2,558 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug feature: cards
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Describe the bug
move card: target could be invalid, cause it's not checked after change of target board

To Reproduce

  1. Create a board with list L1
  2. Create a board without list L1
  3. Create a board with a card
  4. Open "move card"
    4.1 select board: "board with list L1"
    4.2 select list: "L1"
    4.3 change selected board to "board without list L1"
    5: See: List name of target is still L1, even there is no list L1

Expected behavior
After changing the target board, clear the target list (or check it)

Perhaps throw an error (some kind of HTTP 400)? This might prevent data loss, ... when using sync clients

Screenshots
m3

m2

m1

Contributor guide

Open the contributing guide

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

Reproduce the move-card flow with a board containing list L1 and another board without it, then inspect the board and list selection entry points involved in that dialog. Done means changing the target board clears or validates the previously selected list, and invalid targets cannot cause data loss or be accepted silently.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
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.