-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Parse ID3 metadata #4409
feat: Parse ID3 metadata #4409
Conversation
153b727
to
e9fb584
Compare
Incremental code coverage: 92.63% |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like a good start. The links to the ID3v2 spec were very helpful in understanding the parser.
All changes have been tested with multiple streams (including DAI). I wait for a revision to add the tests and not waste time if there are big architectural changes (I hope not...) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one small nit in a test. Looks great!
const Id3Generator = shaka.test.Id3Generator; | ||
const Uint8ArrayUtils = shaka.util.Uint8ArrayUtils; | ||
const result = Uint8ArrayUtils.concat( | ||
Id3Generator.stringToInts_(type), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to see an assertion that type is 4 characters long. That would cause a test case to fail if there is a typo in the frame type when calling generateId3Frame.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
Thanks @joeyparrish ! |
No description provided.