This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
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.
Second in a series of PRs that builds towards a full-fledged programmatic style API. This is a big chunk of work, but I'm trying to break it up step by step and not create a long-lived branch with a lot of changes.
This change introduces subclasses of
StyleLayer
, one for each layer type. Each subclass holds an instance of the appropriate___PaintProperties
that we introduced in the previous commit. That means we can eliminate theStyleProperties
variant. (Well, not completely:ShapeAnnotation
still uses a version reduced to varying betweenLinePaintProperties
andFillPaintProperties
.)We can also move the explicit instantiations of
StyleLayer::applyStyleProperties
(one for each layer type) into pure virtualStyleLayer::applyStyleProperties
and subclass implementations. Future commits in this series will make similar changes, replacingswitch
ortemplate
polymorphism with good old type polymorphism.👀 @kkaefer @brunoabinader