This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Add documentation for data-driven styling #7924
Labels
Milestone
Comments
boundsj
added
iOS
Mapbox Maps SDK for iOS
macOS
Mapbox Maps SDK for macOS
release blocker
Blocks the next final release
runtime styling
labels
Feb 2, 2017
52 tasks
We should fill out the documentation before the first beta, because that's when we tell developers to start coding against new features in nontrivial projects. We can ship an alpha without the documentation if necessary to meet time commitments, however. |
10 tasks
boundsj
added
beta blocker
Blocks the next beta release
and removed
release blocker
Blocks the next final release
labels
Feb 3, 2017
This was referenced Feb 3, 2017
|
#7931, #7943, and #7960 added API documentation that should be suitable for the beta release. We still need a PR to update the guides but I don't consider that a requirement for the beta. Before I create the beta, I will wait for:
|
boundsj
added
release blocker
Blocks the next final release
and removed
beta blocker
Blocks the next beta release
labels
Feb 9, 2017
#8025 will update the MGLFeature documentation to discuss more ways a feature’s attributes can be used, including in source functions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Support for data-driven styling for iOS and macOS is being added in #7596. After we have used the API proposed there and before the final Mapbox iOS SDK 3.5.0 beta, we will fully document the new APIs added for DDS.
This will include (at least):
MGLStyleValue
(as a class cluster it represents something different now)MGLDocumentationExampleTests.swift
to use camera functions and maybe add examples forsource
andcomposite
functionsguides/For Style Authors.md
with DDS specific terminology differencesguides/Runtime Styling.md
with information about DDS (or add a DDS specific guide)cc @friedbunny @jmkiley @1ec5 @incanus @ericrwolfe @pveugen
The text was updated successfully, but these errors were encountered: