Allow custom `engine`

Question

Allow custom `engine`

tjhorner opened this issue 3 years ago · 3 comments

Since the fine-tuning endpoints are out, the engine can be an arbitrary string. This library should either use the engines endpoint to determine the list of available engines (rather than hardcoding them) or just allow any arbitrary string for an engine.

Answer 1 · 2021-08-12T18:33:28.000Z

Thanks, I will open a PR to fix this.

Answer 2 · 2021-08-15T12:48:46.000Z

seconding this! let me know how I can help

Answer 3 · 2021-08-17T22:52:43.000Z

Fixed in v1.2.5