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
At the moment, the "Enabled" flag is hidden behind the "Version" group. So if the "Version" group is closed, you don't see it:
Only if you open the "Version" group, you can see the "Enabled" flag:
This has already led to the situation, where developers said "the extension doesn't work", even though the extension was simply disabled.
IMHO, the "Enabled" flag should be more visible. Either in a separate group or in the "API Details" group or by renaming the "Version" group. However, it is just very unexpected having to open a "Version" group in order to enable the extension.
The text was updated successfully, but these errors were encountered:
Thanks for bringing up this point, @sprankhub. I agree with your point and it could be that simply changing the tab name to "General" might suffice. I'll touch base with the team to ensure we improve on this. Thanks!
Frank-Magmodules
changed the title
UX Flaw: Enabled Flag Hidden Behind Version Group
[IMPROVEMENT] UX Flaw: Enabled Flag Hidden Behind Version Group
May 15, 2024
Hi There @sprankhub , happy to share that we have implemented your request into this new release.
Thank you for sharing this improvement, it made perfect sense. I'm closing this issue for now, talk soon :)
At the moment, the "Enabled" flag is hidden behind the "Version" group. So if the "Version" group is closed, you don't see it:
Only if you open the "Version" group, you can see the "Enabled" flag:
This has already led to the situation, where developers said "the extension doesn't work", even though the extension was simply disabled.
IMHO, the "Enabled" flag should be more visible. Either in a separate group or in the "API Details" group or by renaming the "Version" group. However, it is just very unexpected having to open a "Version" group in order to enable the extension.
The text was updated successfully, but these errors were encountered: