Add Tag::take_filter() #414
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
| I have added some comments. Preserving the order of all items while splitting them is an important feature. |
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.
The behavior of the
take_string()and other string accessor methods has changed in lofty v0.20.0. They now return values from allTagItems, regardless of their description. This is unexpected for ID3v2 tags where the description is meaningful. RegularTagItems usually have an empty description.The new methods are needed to extract only regular
TagItems with an empty description from an ID3v2 tag. The example demonstrates how to achieve this forItemKey::Comment.