Currently, every agent needs an associated .yaml file during the stub generation phase during ventis build, which adds user complexity that can be phased out, as the agent file itself contains all the information the .yaml file contains too, just more easily reachable.
In cli.py on line 184, the .yaml files are first called, in which a seperate function generate_stub is called in the stub_generator.py file. This function calls the _build_stub_method and _build_stub_class functions, both of which have the .yaml content as an input and use that content.
A possible fix would be to add a function call in cli.py before generate_stub is called, which would go through the agents python file and recreate a temporary dictionary with the values needed for the subsequent functions.
If the .yaml file would eventually contain something that the agent .py file doesn't naturally contain already, we can maybe add a new section inside the agent.py file or a field that could be filled out, rather than requiring the user to create a whole seperate .yaml file.
Currently, every agent needs an associated .yaml file during the stub generation phase during ventis build, which adds user complexity that can be phased out, as the agent file itself contains all the information the .yaml file contains too, just more easily reachable.
In cli.py on line 184, the .yaml files are first called, in which a seperate function generate_stub is called in the stub_generator.py file. This function calls the _build_stub_method and _build_stub_class functions, both of which have the .yaml content as an input and use that content.
A possible fix would be to add a function call in cli.py before generate_stub is called, which would go through the agents python file and recreate a temporary dictionary with the values needed for the subsequent functions.
If the .yaml file would eventually contain something that the agent .py file doesn't naturally contain already, we can maybe add a new section inside the agent.py file or a field that could be filled out, rather than requiring the user to create a whole seperate .yaml file.