-
Notifications
You must be signed in to change notification settings - Fork 101
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: improve parsing for a frame-rate attribute #150
Conversation
The PR is related to this videojs/mpd-parser#159 |
This looks good @gjanblaszczyk , thank you. The only concern I have is that it technically breaks the old output. Although it should be minor, and is more appropriate as a number, we should consider a small major for this. |
Yeah, technically a breaking change. Don't see a problem with making a major version of m3u8-parser, though. |
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 needs a BREAKING CHANGE:
in the footer when we merge.
@gkatsev Is it enough to add this footer message during GitHub squash and merge action? or maybe I should do something more... |
yup, that would do it. I rarely if ever merge locally anymore and we prefer squash+merge in the video.js projects. |
BREAKING CHANGE: parser changes an output type for 'FRAME-RATE' attribute from a string to a number.
This reverts commit d51e93f.
The 'FRAME-RATE' attribute should be a floating-point number type rather than a string.