MagiCircles / MagiCircles/SchoolIdolAPI

Suggestion about filters under "Account"

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

Nobody has claimed this yet.

Dominant language
Python
Stars
151
Forks
29
PR merge metrics
No merged PRs in 30d

Description

1. Please add "Waiting Room" under Stored filter.

I move promo cards which I finished max level and max bonded because I want to keep them but I don't use them in my decks. I also keep cards which I idolized and threw away in the past when my deck was not big enough to keep cards that I don't use, to complete a set someday.
It's hard to manage them because they all are in deck with current Sukutomo.

2. Please change filter options into checkbox and radio.

All filter options under Account (Stored, Idolized, Max Leveled and Max Bonded) are using drop-down list. I'd like to suggest to change them into checkbox and radio buttons.

For Stored: It'll be nice if this filter option is checkbox because I can filter cards which I really have in deck and present box at once. Even for waiting room if suggestion #1 is accepted.

For others: They have only 3 options for each filter. So I can set a filter by one click. Dropdown list makes me click two times to set a filter. Option text can be very short as below.

Idolized
○ Yes ○ No ◉ Both
Max Leveled
○ Yes ○ No ◉ Both
Max Bonded (Kizuna)
○ Yes ○ No ◉ Both

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

The issue names no files, tests, or entry points, so first locate the Account filter implementation and related test coverage. Done means Stored supports the requested Waiting Room behavior and checkbox controls, while Idolized, Max Leveled, and Max Bonded support the specified Yes, No, and Both choices.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.