Updating documentation for Preset names and Preset 0.#284
Open
MichaelCrimando wants to merge 1 commit intosmartdevicelink:masterfrom
Open
Updating documentation for Preset names and Preset 0.#284MichaelCrimando wants to merge 1 commit intosmartdevicelink:masterfrom
MichaelCrimando wants to merge 1 commit intosmartdevicelink:masterfrom
Conversation
Author
|
@theresalech can you give this a review plz? |
Member
|
@MichaelCrimando the README.md is generated from the actual xml file MOBILE_API.xml . Sorry this can be a bit confusing. The XML file is the source of truth, we generate the README from it, then copy that into the developer portal. |
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
2 participants
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.
A current problem we're having is that there's no consistent documentation with preset 0. Should it be first in the preset list or last? This matters if you're setting custom preset names, since the app just sends an array of strings to name the presets. So if preset 0 is in the wrong spot, it throws off all the preset names. Currently Pandora considers it as preset 10 vs iHeartRadio considers it as preset 0.
This came up because we've never had a sync that can use 10 presets AND show the preset label.
sync3 only does presets 1-8 and shows labels.
sync1 does 10 presets but no labels