Deprecate the module

Created on 28 January 2025, 3 months ago

Problem/Motivation

With the AI module doing most functionalities that are in this module (and much much more)

Would it not make sense to close this module and point the people to the AI module?
- Less maintenance work for the maintainers of this project(less duplicate code)
- Less maintenance work for the maintainers of this project (as the maintainer of this one can help there).

Obviously you may close this if you think it is a bad idea.

How could this be implemented?
0 Check for feature parity and make the missing features (I think the image generation is not there in the same way yet) as a separate module.
1 Add the dependency for the AI module and the openai provider module (and the ai_newly_created_module module)
2 (if you want to provide an upgrade path) Make a update hook/script that moves the config for the KEY, and automatically configures the AI module with the settings you had for this module.

It's just an idea Obviously you could keep on supporting this module, but it is still tied to openai, and at the AI module you have deepseek, mistral, and also openai available.
let me know what you think.

🌱 Plan
Status

Needs work

Version

2.1

Component

Code

Created by

🇧🇪Belgium wouters_f Leuven

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024