Fix common Lyric/Text problems #1053
Merged
Conversation
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
|
|
||
| allText = [ly.text for ly in self.lyrics] | ||
| return '\n'.join(allText) | ||
| return '\n'.join([t for t in allText if t is not None]) |
Member
There was a problem hiding this comment.
This solves the crashy part of #1036 but would still be worth a small think over how empty values should roundtrip, i.e. as empty string or None, because right now = inconsistent. Just mentioning in case you're feeling opinionated.
Member
Author
There was a problem hiding this comment.
in this case, it's a short-hand so it's not a big deal if it doesn't roundtrip perfectly, since it also doesn't preserve which lyric each syllable (or composite) comes from.
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.
No description provided.