Fix #725 - correctly parse tags on json import - #908
Merged
Conversation
|
This pull request introduces 1 alert when merging 4b8962b into 9899377 - view on LGTM.com new alerts:
|
Member
|
Thanks @hannah98 !!! |
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
2 participants
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.
Summary
This PR fixes #725 - instead of tags being split on each character, this fix mimics a code block further down in the same file to create a list of tags first before calling the
save_tags()method.ArchiveBox/archivebox/index/sql.py
Lines 107 to 109 in 3276434
Related issues
#725
Changes these areas