Skip to content
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

Issue warning if PKL does not contain assets of type "text/xml" #380

Merged
merged 4 commits into from
Sep 27, 2024

Conversation

fschleich
Copy link
Contributor

@fschleich fschleich commented Sep 10, 2024

PKLs are not required to reference any CPL/OPL files, but they typically do. This update adds a WARNING if a PKL does not contain any assets of type "text/xml".

Resolves #303.

- not depending on correct mime type in PKL in order to identify referenced files as OPL or CPL
- instead looking at all non-MXF assets to find CPLs/OPLs and THEN validating that their mime type is stated correctly in the PKL
…beled as text/xml

CPL/OPL parsing will continue to depend on the correct mime type in PKL, but a warning is provided if a PKL does not contain any assets of type text/xml
@fschleich fschleich changed the title Validating mime type for CPL and OPL assets Issue warning if PKL does not contain assets of type "text/xml" Sep 13, 2024
@fschleich fschleich marked this pull request as ready for review September 14, 2024 00:11
…ApplicationCompositions

- in case implementation of analyzeApplicationCompositions won't depend on mime type in the future
@fschleich fschleich merged commit 18965f2 into master Sep 27, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PKL MIME issue not recognized
1 participant