Strip the configuration of unwanted values before saving.

Created on 21 November 2024, 1 day ago

Problem/Motivation

Currently we have something that gives the structure of how a config should be defined in YAML and what each of the fields does. We also give few shot learning examples that might differ from the structure of the current YAML.

The bug we found was for instance a paragraph handler being created and a few shot learning of a taxonomy handler. This made the AI think it made sense to add auto_create: false to it, which it should not have.

This can somewhat be fixed with prompting, but an AI will always be hallucinating somewhat how this could be generated, specifically when you have few shot learning showing it something similar.

It is very very unlikely that it will forget some configuration, but it might add configurations that shouldn't be there.

We need to strip them post generation.

Steps to reproduce

Try generating paragraph fields.

Proposed resolution

Check the created configuration post generation and strip it of any configuration that is not set by the wanted structured that we asked for before saving.

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Version

1.0

Component

Code

Created by

🇩🇪Germany marcus_johansson

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

Comments & Activities

  • Issue created by @marcus_johansson
  • 🇩🇪Germany marcus_johansson

    We should make the fetching of the configuration, so the thing that looks at defaultConfiguration and the form of a PluginConfiguration entity and this method into general methods instead of having them in the field agent.

    So you can just provider the entity class to do this.

Production build 0.71.5 2024