- Issue created by @j-barnes
- Merge request !30Issue #3454051: Added basic token eca action and submodule. → (Open) created by j-barnes
- Status changed to Needs review
16 days ago 10:55pm 11 June 2024
It would be awesome if we could add a basic token action for Augmentor. We would only need it to handle an input token and an output token so we can take full advantage of ECA. For example, we could automatically set site descriptions to the metatag module fields. Right now, this isn’t possible with the minimal Augmentor action (json_encode nested fields).
By keeping it simple, it really allows us to fully leverage what ECA has to offer and explore other modules like ECA Tamper to create the data manipulations ourselves. For example, when generating tags we may want to see a list of tags we have already curated and select one of those before generating a new one. This is easily solvable through built in ECA functionality if we had this feature.
I think it would make sense to create this as a submodule, especially since it would depend on the ECA module, and not everyone might need that. We could create a base action that contains the manditory fields such as input token, output token, augmentor, and key. This would allow us to extend and create different flavors of actions (maybe injecting additional information into the prompt or passing other field input besides what already lives in our augmentor).
Example of ECA use case:
Example of ECA Action:
Needs review
1.1
Code