feat: add remove license command #1791
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
latekvo
approved these changes
Dec 5, 2025
|
|
||
| export interface ProjectEventMap { | ||
| projectStateChanged: ProjectState; | ||
| licenseActivationChanged: boolean; |
Member
There was a problem hiding this comment.
Is this change relevant to this PR?
Collaborator
Author
There was a problem hiding this comment.
no but i noticed it working on it. It is a dead code from previous state management approach
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.
Now that there is a noticeable difference between experience of activated and un activated license we add a "remove license" command with two goals in mind:
How Has This Been Tested:
Screen.Recording.2025-12-05.at.15.53.55.mov
How Has This Change Been Documented:
We have quite a large trouble shooting backlog to document we will handle it all at once in a future PR