Fix Session Buddy import so that it accounts for "current", "previous", and "saved" session type properties
#1071
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
|
FYI @sienori 😄 |
|
@sienori why this PR isn't part of the updates? |
|
Thank you for you pull request! Sorry for my late reply. |
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.
Resolves #912.
Now when exporting Session Buddy sessions, all four export options will work when imported into TSM:
Note: the Session Buddy "Back up" option still produces a format that TSM cannot import:
I was going to address the back up issue as well, but decided that this PR will fix my use-case for now. 😅 I imagine the back up fix will be very similar: verifying that the back up JSON file has all of the correct keys and such.