[Dashboard][Feature request] Turning off extensions should make widget disappear (or something) and not be able to be added

[mathewleeza]

Dev Home version

No response

Windows build number

No response

Other software

No response

Steps to reproduce the bug

Description

1. have widgets on dashboard
2. turn off GitHub ext
3. widgets remain on
4. click "Add" and they still are able to be added

widgets shouldn't be present as Dev Home shouldn't 'see' the extension anymore

This is a complicated problem, and unlikely to make it for Build. We want users to know that we know that it's a problem, so we can create a public GitHub issue for it right when we release.

Can we have PM decide on functionality here? (And it's a big enough decision I think it should be documented.) The suggestion in this bug is not inherently correct (even if we decide it's the functionality we want). DevHome knows about these widgets because the extension registered the widgets with the widget platform. It has nothing to do with the extension's communication with the core app.

If you decide to do this, it severely limits third party widgets in the future. You'd be saying "to have a widget in DevHome, you have to write a DevHome extension". You couldn't write your own app and have DevHome display your widget. Obviously made up example, but if we weren't doing our own ADO widgets, ADO could never write a native client that included a widget used in DevHome. They'd HAVE to also write an extension.

Expected result

No response

Actual result

No response

Included System Information

No response

Included Extensions Information

No response

[krschau]

Related but not dupe of #1390

[krschau]

Duplicate of #3252

[microsoft-github-policy-service]

We've identified this as a duplicate of another one that already exists. This specific instance is being closed in favor of tracking the concern over on the the linked issue. Please add your 👍 to the other issue to raise its priority. Thanks for your report!