Add ergonomic typed extraction and rewrite APIs#1
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR adds a thin ergonomic API layer on top of the existing low-level
mp4forgeprimitives for common path-based extraction and rewrite workflows.What changed
extract_box_asextract_boxes_asextract_boxes_as_with_registryrewrite_box_asrewrite_boxes_asrewrite_boxes_as_with_registry0.2.0and updated release-facing metadata and changelogWhy
The low-level API was already solid, but common read/edit flows still required too much boilerplate. These helpers keep the existing architecture intact while making typical typed workflows easier to write, easier to read, and easier to debug.