Fix TrialTimeRemaining documentation to clarify behavior for different trial types #2503
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
TrialTimeRemainingproperty documentation was misleading and contained a fundamental conceptual error that could cause developers to implement incorrect trial logic.The Problem
The original documentation described
TrialTimeRemainingas being specifically for "usage-limited trials":However, this is contradictory because:
ExpirationDateproperty explicitly documents that usage-limited trials return "December 31, 9999"This contradiction led to confusion about when and how to use the
TrialTimeRemainingproperty effectively.The Solution
Updated both
StoreAppLicense.TrialTimeRemainingandStoreCollectionData.TrialTimeRemainingdocumentation to:Key Changes
IsTrial,ExpirationDate)This brings the documentation in line with the actual API behavior and prevents developers from implementing incorrect trial logic based on the misleading original documentation.
Fixes #1764.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.