The documentation says remove conversation: from the yaml. It’s not there and I have remove the default_config:
This seems outdated:
Please advise.
The documentation says remove conversation: from the yaml. It’s not there and I have remove the default_config:
This seems outdated:
Please advise.
Is the documentation wrong? Is their really no way to remove it now?
The way you remove it is to stop using Default Config.
This was discussed, exhaustively, in a previous FR thread.
Yes, but the phrase “It’s not there and I have remove the default_config:” is not a question… it is two true statements. It is true that conversation:
is not explicitly in configuration.yaml
because it is included through default_config
. And you are also correct that you have to remove default_config:
if you wish not to have the Conversation integration automatically configured.
With your “please advise”, I assumed you were asking what actions you should take to help update the documentation.
If that is incorrect, what are you trying to convey?
Ok, I wasn’t explicit.
One of the devs says that the integrations can load other integrations. Why they do this without throwing some sort of error or warning, I don’t know. I went through the list and removed the few they said. No luck killing it.
The docs for this integration say that it’s needed in either default_config or yaml added, and undocumented with some other integrations that also don’t document the requirement.
For something used by 3.9% of the installs to be forced like this is disappointing. I’m going to walk away from this problem. It’s pretty clear this is a requirement someplace for reasons.