Suggestion...

If the configuration were to be per-block-instance then we could have different configs for different scenarios, including roles.

I appreciate that this might mean adding a block ID 'key' in the DB table relating to the configuration per block but the benefits of the feature would probably significantly outweigh the coding refactoring work to get it in place.

Issue fork ai_content_chat-3574756

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

sirclickalot created an issue. See original summary.

sirclickalot’s picture

sirclickalot
Primary language English
Location Somerset
commented
Issue summary: View changes
solimanharkas’s picture

solimanharkas commented

Thanks for the suggestion, agree, this will go into v3.0.

Global settings (AI provider, model, prompt, etc.) will stay as site-wide defaults. Each block can optionally override any of those. Content sources will be per-block only, since that's the whole point, different blocks, different content.

Simple sites just configure globally and pick content sources per block. Advanced setups can override provider or prompt on specific blocks.

Breaking change from v2, no auto-migration, but minimal, admins just need to set content sources on their existing block.

Let me know what you think, or if you have a different approach in mind.

solimanharkas’s picture

solimanharkas commented
Version: 1.0.1 » 2.0.0
sirclickalot’s picture

sirclickalot
Primary language English
Location Somerset
commented

Hi @solimanharkas

Yep, that all said exactly the right approach to me.

Enable the 'single use' as before but enable 'variations of it'.

Nice!

solimanharkas opened merge request !11

solimanharkas’s picture

solimanharkas commented
Status: Active » Needs review