External/card-drop

Dropnumber command isn't finding cards even though they exist #108

New issue

Closed

opened 2023-12-09 17:00:24 +00:00 by Vylpes · 0 comments

Vylpes commented

2023-12-09 17:00:24 +00:00

Owner

No description provided.

Vylpes added this to the 0.3.0 milestone 2023-12-09 17:00:36 +00:00

Vylpes added the

label 2023-12-09 17:00:46 +00:00

Vylpes self-assigned this 2023-12-09 17:00:51 +00:00

Vylpes added this to the 0.3 Sprint 2 project 2023-12-09 17:00:53 +00:00

Vylpes added

and removed

labels 2023-12-09 17:01:20 +00:00

Vylpes referenced this issue

2023-12-09 17:01:30 +00:00

AS a developer, I want the card setup functions to use JSON files to determine the metadata for a card #27

Vylpes removed this from the 0.3 Sprint 2 project 2023-12-09 17:01:34 +00:00

Vylpes started working 2023-12-09 17:01:47 +00:00

Vylpes stopped working 2023-12-09 17:16:18 +00:00

14 minutes 31 seconds

Vylpes closed this issue

2023-12-09 17:16:22 +00:00

Vylpes referenced this issue

2023-12-09 17:18:46 +00:00

Fix dropnumber command #109

Vylpes referenced this issue from a commit

2023-12-09 17:18:54 +00:00

Fix dropnumber command (#109)

Sign in to join this conversation.

No labels

requires documentation

No milestone

No project

No assignees

1 participant

Notifications

Total time spent: 14 minutes 31 seconds

Vylpes

14 minutes 31 seconds

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: External/card-drop#108

No description provided.