You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Settings -> Labs section is only shown when "showLabsSettings": true, is configured in the Element config.json which not every Element instance has activated. The Labs section is also shown for any active "Betas" but only shows the betas and not the feature toggles unless the showLabsSettings setting is also true.
Feature flags can still be toggled manually via the devtools console if you know the JavaScript magic necessary to make it happen. But this is cumbersome to lookup, figure out which toggle you want, and use every time.
If I've toggled /devtools -> Developer mode, then that should give enough indication that I want and am capable enough to handle the dangers of the Labs feature toggles.
How would you like to achieve it?
When developer mode is enabled, always show Labs feature toggles
Your use case
Problem
Currently, the Settings -> Labs section is only shown when
"showLabsSettings": true,
is configured in the Elementconfig.json
which not every Element instance has activated. The Labs section is also shown for any active "Betas" but only shows the betas and not the feature toggles unless theshowLabsSettings
setting is alsotrue
.Feature flags can still be toggled manually via the devtools console if you know the JavaScript magic necessary to make it happen. But this is cumbersome to lookup, figure out which toggle you want, and use every time.
If I've toggled
/devtools
->Developer mode
, then that should give enough indication that I want and am capable enough to handle the dangers of the Labs feature toggles.How would you like to achieve it?
When developer mode is enabled, always show Labs feature toggles
Have you considered any alternatives?
No response
Additional context
This idea already has some buy-in and discussion in an internal room
Dev notes
The text was updated successfully, but these errors were encountered: