-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate CHE_API_EXTERNAL #15697
Deprecate CHE_API_EXTERNAL #15697
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm 👍 on the change, but would like feedback from others on the decision before merging.
Can one of the admins verify this patch? |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
It should not be linked to CheApiInternalVarProvider. It is used for communication with external web browsers. Signed-off-by: Masaki Muranaka <[email protected]>
Actually, `CHE_API` is actively used. Signed-off-by: Masaki Muranaka <[email protected]>
Signed-off-by: Masaki Muranaka <[email protected]>
As `CHE_API_EXTERNAL` was deplicated. Signed-off-by: Masaki Muranaka <[email protected]>
What does this PR do?
Moves
deprecated
flags fromCHE_API
toCHE_API_EXTERNAL
.This is a first step of removing
CHE_API_EXTERNAL
.What issues does this PR fix or reference?
CHE_API_EXTERNAL
.che.api.{external,internal}
if exist. #13774 .