Support new extended history filenames #280
Closed
Conversation
This file contains 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
mitchwilliamson
changed the title
|
I just got my extended streaming history data today and it doesn't follow either of those patterns for some reason
|
|
I've just had mine through and have a combination of the two 
|
|
I added a fix in 1.7.1 so this is not up to date anymore. Also I feel like the file names will continue to change. We will maybe need to check the content of the file rather than the filename. |
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.
This addresses #279 which I also encountered from an export generated today. The extended history importer now supports files with either
endsongorStreaming_History_Audioprefixes.