-
Notifications
You must be signed in to change notification settings - Fork 142
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
♻️ [RUMF-1529] use an enum for experimental features #2113
Conversation
361fba3
to
22b1acf
Compare
Codecov Report
@@ Coverage Diff @@
## main #2113 +/- ##
==========================================
- Coverage 93.67% 93.48% -0.19%
==========================================
Files 163 163
Lines 5691 5711 +20
Branches 1303 1310 +7
==========================================
+ Hits 5331 5339 +8
- Misses 360 372 +12
... and 2 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
||
export function updateExperimentalFeatures(enabledFeatures: string[] | undefined): void { | ||
export function updateExperimentalFeatures(enabledFeatures: ExperimentalFeature[] | undefined): void { |
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.
🥜 nitpick: This function cannot update (disable) a feature already present. Maybe we should name it addExperimentalFeatures ?
Let's define the `enabledExperimentalFeature` during module evaluation. This way, we don't need to worry about it being undefined. Also, we are now validating `enabledExperimentalFeature` configuration in `configuration.ts`, so move validation tests there.
Motivation
Improve typecheck, helps to clean flags when enabling them.
Changes
Use an enum for experimental features
Testing
I have gone over the contributing documentation.