Updating pricing tier documentation reference #35
Conversation
This file contains 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
|
@HowardWolosky, |
The config files that are generated document what the pricing json is supposed to look like, but there's a TODO in place for determining how a price maps to a "tier" enum value. Adding in the reference to the API documentation that explains how to get that Tier information.
HowardWolosky
force-pushed
the
fix/pricing
branch
from
b526c46 to
50f1cef
Compare
danbelcher-MSFT
approved these changes
Mar 9, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The config files that are generated document what the pricing
json is supposed to look like, but there's a TODO in place for
determining how a price maps to a "tier" enum value.
Adding in the reference to the API documentation that explains
how to get that Tier information.