Skip to content
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

[OSS101] Task 9: A mechanism to remotely disable broken features #813

Open
tyn1998 opened this issue May 12, 2024 · 0 comments
Open

[OSS101] Task 9: A mechanism to remotely disable broken features #813

tyn1998 opened this issue May 12, 2024 · 0 comments

Comments

@tyn1998
Copy link
Member

tyn1998 commented May 12, 2024

Description

HyperCRX is a browser extension, and the release process for browser extensions differs from that of typical web projects due to the requirement for approval from browser extension stores. Currently, the approval process in the Chrome Store can be completed within half an hour, but the Edge Store often takes about a week, which can be disastrous. Sometimes, due to updates on GitHub, some features of HyperCRX may break. Even if developers can fix the issues promptly, Edge users have to wait a week to see the issues resolved due to the approval cycle, leading to user attrition.

The Refined GitHub community has their solution, yolo, which enables remote feature toggling. This task requires implementing a mechanism in HyperCRX that can remotely disable features, inspired by yolo.

任务描述

HyperCRX 是一款浏览器扩展,浏览器扩展的发布不同于普通 Web 项目的发布,因为每一次新版本的发布都需要经过浏览器扩展商店的审批。目前,Chrome 商店的审批能在半小时内完成,但是 Edge 商店的审批往往需要一周左右的时间,这是一场灾难。有时候,由于 GitHub 的更新,HyperCRX 的一些特性会挂掉,即使开发者能及时修复问题,但由于审批周期的存在,Edge 用户也需要等到一周后才能看到问题被修复,这会导致用户流失。

Refined GitHub 社区有他们的解决方案 yolo。该任务要求参考 yolo 在 HyperCRX 中实现一个可以远程关闭特性的机制。

@tyn1998 tyn1998 changed the title [OSS101] Task 9: [OSS101] Task 9: A mechanism to remotely disable broken features May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant