Add support for AI powered solutions

Hey Dieter, great idea. We should probably collaborate that in this module, that way you we aren't duplicating work.

https://www.drupal.org/project/openai →

There is a submodule for openai_dblog for example. I also had some thoughts here:

https://www.drupal.org/project/openai/issues/3338718 ✨ Add ability to manually add 'solution' to a watchdog log Closed: won't fix

I think we are on the right path here - but may make more sense as a submodule in that suite. Or require that module here... one or the other.

I’m not sure you completely understand my intention here. This functionality was added to the Ignition package, all we would need to do is bridge it to this module through configuration. I don’t think that little code/configuration needs to be part of the OpenAI module, there won’t be any custom logic.

Working on this.

TY very much for review changes and feedback. I ll get back to work on this asap.

Ready for review!

Looks good! I think we should wait for the following upstream issues to be fixed before actually releasing this:

• https://github.com/spatie/ignition/issues/263
• https://github.com/spatie/ignition/issues/264

Or what do you think?

Could the Markdown module be used to convert an incoming response from HTML?

That's not up to us to fix, it should be fixed upstream. I noticed this in the changelog of 1.6.0 though:

Add support for rendering markdown in solutions

This should probably be tested again with the latest version of the package.

I just tested again with the latest version of the Ignition library. It seems like #263 is fixed, #264 isn't but I created a PR: #302. This is what the output currently looks like with the code from the PR:

Let's wait until the other issue is fixed before merging this.

Like I said in my previous comment, #264 is not fixed yet. We could just ignore that, release this feature and fix it in a follow-up though.

That issue is now actually fixed and releases, so this is now unblocked. Will try to finish ASAP.

Apparently the Key module provides a built in way → to override any config value, so I don't think it's necessary to add explicit support here. There are many ways to override config, including Drupal core's way.

Automatically closed - issue fixed for 2 weeks with no activity.