ExtensionDiscovery has a lot of behavior and possible states that is currently not covered by tests.
Some of this may be intended, some if it may be bugs.
I think the correct thing to do is to cover the current behavior with tests, and only then consider fixing things. This way we see exactly which behavior is changing.
This does not break anything or modify existing behavior, so it can go into 8.1.x.
Needs work
10.1 ✨
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
Tagging for IS update as a lot has changed in 7 years so this issue may need to be rescoped.