Repository navigation
feat(pro): free upgrade preview with counts and the Pro link - #57
Merged
Merged
Conversation
…of a bare pro_required
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
1 participant
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 free user who asks for the upgrade report now gets a local preview instead of a bare pro_required: how many of the APIs the project calls change (removed, renamed, re-signed, deprecated), across how many call sites, one sample, then the Pro price and link. The answer still carries structuredContent.pro_required, so agents can tell the user. The full report (each change, its replacement and every call site) stays Pro. The preview uses the existing report path, so download opt-ins are unchanged and it makes no new network calls. pro::PRICE is checked against the pricing page by a test.
Licensed output is unchanged.