Add source virtual integration to config flow context

[zweckj]

Breaking change

Proposed change

Add the original virtual integration to the config flow context, to be used for branding (later) or different config flow actions.

Core PR: home-assistant/core#132471
Arch discussion: home-assistant/architecture#1160

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[silamon]

Run prettier to get CI green.

[bramkragten]

We will now have the context for some cases but not all, for example, a discovered device, or adding a config entry on the integration page, will not have this context. Not sure how we are planning to use this, but feels a bit half now?

[zweckj]

We will now have the context for some cases but not all, for example, a discovered device, or adding a config entry on the integration page, will not have this context. Not sure how we are planning to use this, but feels a bit half now?

Then I just missed some places, never touched anything in the frontend before. I think I know where the integration page thing is. Discovery should not be relevant atm, as virtual integrations can’t discover (as their virtual part) I believe.

[bramkragten]

We will now have the context for some cases but not all, for example, a discovered device, or adding a config entry on the integration page, will not have this context. Not sure how we are planning to use this, but feels a bit half now?

Then I just missed some places, never touched anything in the frontend before. I think I know where the integration page thing is. Discovery should not be relevant atm, as virtual integrations can’t discover (as their virtual part) I believe.

Not sure if they are missed, the places I mention do not have a notion of virtual integrations, as they are now only used for findability, but it sounds like these PRs trying to change that. So I wonder what it will be used for, like branding is nice, but it is weird if some things will be branded correctly and others are not.

[zweckj]

Not sure if they are missed, the places I mention do not have a notion of virtual integrations, as they are now only used for findability, but it sounds like these PRs trying to change that. So I wonder what it will be used for, like branding is nice, but it is weird if some things will be branded correctly and others are not.

I meant this other place https://github.com/home-assistant/frontend/blob/dev/src/panels/config/integrations/ha-config-integrations-dashboard.ts#L885-L921, here we do know about virtual integration apparently (but I'm not really sure what it's used for tbh). Branding would be a second step anyway. First step is to allow the config flow to react on that info, when we are configuring a virtual integration.

[bramkragten]

The code you linked is what is used when you add an integration with a my.home-assistant.io link, so yes, that needs to be handled.