Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Better import handling: try to import all cards, and show to the user those which cannot be imported #685

Open
Altonss opened this issue Dec 14, 2021 · 2 comments
Open

Better import handling: try to import all cards, and show to the user those which cannot be imported #685

Altonss opened this issue Dec 14, 2021 · 2 comments
Labels
common: uncommon Most users are unlikely to come across this or unexpected workflow severity: minor Impairs non-critical functionality or suitable workarounds exist type: enhancement New feature or request

Comments

@Altonss
Copy link
Contributor

Altonss commented Dec 14, 2021

I thought about a possible enhancement related to the issue #661 . Instead of just quitting the whole import, we could import the cards that are "compatible"/"readable" by the import script and just don't import the once that fails. After the import a popup could show up saying: "1 card could not be imported because of a formatting error".
But this is just an enhancement idea and not a priority at all :)
@TheLastProject TheLastProject added the type: enhancement New feature or request label Dec 14, 2021
@TheLastProject
Copy link
Member

I would like to first fix #513, then we can do this more asynchronously too. But yeah, would be nice.

@Altonss
Copy link
Contributor Author

Altonss commented Dec 14, 2021

I would like to first fix #513, then we can do this more asynchronously too. But yeah, would be nice.

I completely agree :) This issue is just to archive some ideas for future development.

@TheLastProject TheLastProject added common: occasional Affects or can be seen by some users regularly or most users rarely severity: major Severely degrades major functionality or product features, with no satisfactory workaround labels Feb 5, 2022
@TheLastProject TheLastProject mentioned this issue Jun 29, 2023
Draft
@TheLastProject TheLastProject added severity: minor Impairs non-critical functionality or suitable workarounds exist common: uncommon Most users are unlikely to come across this or unexpected workflow and removed severity: major Severely degrades major functionality or product features, with no satisfactory workaround common: occasional Affects or can be seen by some users regularly or most users rarely labels Jul 17, 2023
@obfusk obfusk mentioned this issue Oct 15, 2023
Open
49 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
common: uncommon Most users are unlikely to come across this or unexpected workflow severity: minor Impairs non-critical functionality or suitable workarounds exist type: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TheLastProject @Altonss