You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
16
16
17
17
-**APE**: The `Tag` -> `ApeTag` conversion will now preserve multi-value items ([issue](https://github.com/Serial-ATA/lofty-rs/issues/631)) ([PR](https://github.com/Serial-ATA/lofty-rs/pull/633))
18
18
19
+
### Removed
20
+
21
+
-**ItemKey**: `ItemKey::FileType` and `ItemKey::MusicianCredits` ([PR](https://github.com/Serial-ATA/lofty-rs/pull/636))
22
+
- These are ID3v2-specific fields with special formats.
@@ -240,7 +240,7 @@ Converting your concrete tag type into the generic `Tag` involves the following:
240
240
241
241
##### Defining Generic Mappings
242
242
243
-
The `ItemKey` mappings are defined in [src/tag/item.rs](../src/tag/item.rs).
243
+
The `ItemKey` mappings are defined in [src/tag/item.rs](../lofty/src/tag/item.rs).
244
244
245
245
See the comments for the `gen_map!` macro, which explains its use in detail, and will be kept up to
246
246
date with any future changes.
@@ -411,7 +411,7 @@ TODO
411
411
412
412
#### Assets
413
413
414
-
Test assets for tag formats are to be placed in [tests/tags/assets/](../tests/tags/assets).
414
+
Test assets for tag formats are to be placed in [tests/tags/assets/](../lofty/tests/tags/assets).
415
415
416
416
There should at least be one asset, which is a binary file containing the tag below:
417
417
@@ -444,12 +444,12 @@ There are at least 4 unit tests that should be created for every tag format:
444
444
* Using `crate::tag::utils::test_utils::create_tag()`, verify that the converted tag is correct
445
445
446
446
These tests should be placed in the tag's `read` module. If there are many tests, feel free to break them out
447
-
into their own module (ex. See the [ID3v2 `tests` module](../src/id3/v2/tag)).
447
+
into their own module (ex. See the [ID3v2 `tests` module](../lofty/src/id3/v2/tag)).
448
448
449
449
For an example of these tests, see the [ApeTag tests](https://github.com/Serial-ATA/lofty-rs/blob/9c0ea926c690bc6338ba95aceccc4d93e2ee9826/src/ape/tag/mod.rs#L540-L656).
450
450
451
451
#### Integration Tests
452
452
453
453
Integration testing is not normally necessary for tag formats, as they are typically
454
454
tested extensively through the module's unit tests. However, if one wants to create integration tests,
455
-
they can be placed in [tests/tags/](../tests/tags).
455
+
they can be placed in [tests/tags/](../lofty/tests/tags).
0 commit comments