Issue #629: Don't stop yamtrack import on error#630
Merged
FuzzyGrim merged 1 commit intoFuzzyGrim:devfrom Jun 18, 2025
Merged
Conversation
Owner
|
Thank you! I will keep: Because if the user has used an unexpected CSV format, it should stop the import so we don't make unnecessary API requests for each media ID when they won't be able to be imported anyway. |
Contributor
Author
|
I’ll tackle that in a separate PR tomorrow normally! |
Owner
|
It's fine, I will do it. Thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A fix for issue #629
For full transparency: This was generated with the help of Claude Sonnet, I'm not a python developer.