Can we adjust the scope of the project to only be a Chat Model and a service class that can be used to connect with any valid provider in Drupal (provided via Drupal AI module)?

Plan would be to

Remove (as this is already in scope of FlowDrop main project)

- flowdrop_node_category.flowdrop_node_category.ai.yml
- flowdrop_node_type.flowdrop_node_type.chat_output.yml
- ChatOutput Plugin

Rename to "flowdrop_ai_provider" namespace

- flowdrop_node_type.flowdrop_node_type.chat_model to flowdrop_node_type.flowdrop_node_type.flowdrop_ai_provider_chat_model
- Plugin ChatModel to AiProviderChatModel (id can be `flowdrop_ai_provider.chat_model`)

The plugin needs to be updated to latest version of FlowDrop as well.

Issue fork flowdrop_ai_provider-3569410

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

d34dman created an issue. See original summary.

d34dman’s picture

d34dman commented
Title: Adjust shipped configurations to avoid conflict with flowdrop core » Adjust module scope
Issue summary: View changes

d34dman opened merge request !3

d34dman closed merge request !3

d34dman opened merge request !4

d34dman’s picture

d34dman commented
Status: Active » Needs review

  • d34dman committed cb989c7d on 1.0.x 
    Issue #3569410 Make codebase compatible with latest version of FlowDrop
d34dman’s picture

d34dman commented
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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