Feature request: Support for multiple decks
See original GitHub issueIt would be great if there was support for multiple decks.
For example, the syntax for creating a card with apy add
in a deck called “Programming” could be:
deck: Programming
model: Basic
tags: marked
# Note
## Front
## Back
Currently it seems that cards are put into the deck that was last used.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Feature Requests - Brainscape Help Center
Question: Are all my classes and decks saved for future reuse if I cancel my subscription? Natalie Geller; 1 year ago; Edited. 0...
Read more >Feature request: support plugins on a combination of ... - GitHub
Kong allows configuring plugins for any combination of Consumer, Service and Route. These are currently not configurable via deck.
Read more >Better Multi-Monitor Support in Game Mode - Steam Community
Steam Deck > Feature Requests > Topic Details ... Better Multi-Monitor Support in Game Mode. So most importantly, there should be a setting ......
Read more >How our Start-up Handles Feature Requests - The 6Q Blog
Recently, I gave a presentation to a group of founders about our workflow in handling feature requests. I share these slides, and my...
Read more >Feature Request - RoyaleAPI Discuss
Topic Replies Views Activity
About the Feature Request category 2 314 November 9, 2021
Card vs card winrate 4 43 December 15, 2022
Arena Cards ·...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think things work quite well now, and I would be happy if you could test.
Note, as before, please make sure to make backups!
Just to let you know: I’ve started to look at this now. It seems to be quite easy, so I think I will be able to add support for the “deck” syntax in not so long.
I’m not sure how to handle “implicit decks” though. That is, if one does not specify a deck at all, how should
apy
behave? Should it just silently use the active deck? (For me that would be fine.)