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.
Fifth 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 episode moves further towards being able to remove the generic
ClassProperties
in favor of concrete paint and layout classes like those found in style_properties.hpp. The way that I'm going to do that is to continue refactoring until all usage ofClassProperties
is in layer subclasses, and then substitute the concrete per-layer replacements.This PR eliminates
StyleBucket
and moves bucket creation to layer subclasses. Along the way I believe to have fixed #2820, by restoring the previous use of apartialParse
boolean.👀 @kkaefer @brunoabinader