Add support for layer/path metadata inheritance #187
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.
This PR refactors path metadata to support inheritance semantics, including:
PathMetadatafields are nowOption<T>:Nonemeans "inherit from layer" (or SVG default if layer also `None`)LayerMetadata::default_path_metadata: Layer-level defaults that paths can inherit from<g>, path overrides on<path>, letting SVG handle inheritanceResolvedPathMetadata: For display purposes (vsvg-viewer) where concrete values are neededPathMetadata::merge(): Conflict semantics (both Some but different → None)This is part 4 of 4 in a stack made with GitButler:
PathandFlattenedPath#186.buffer()toPathandFlattenedPath#184