You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This came up in discussion of #279.
CLI commands currently parse the template name and take that as a file location, but in practice it may be more helpful to have them accept a pre-parsed object in a process parallel to that of writing (e.g., the output could be YAML or HTML or whatever, but we don't handle that in the command).
This would make it easier for pre- and post-processing functions to know which template is currently being used since it will already be loaded, rather than isolated to a single CLI command.
The text was updated successfully, but these errors were encountered:
or rather, don't use different Engines for different sources, like
GPT4All.
Also address #305 - this is a bit overloaded for a single PR but will be
messy to handle concurrently.
Support for loading local models will be in a different PR.
This came up in discussion of #279.
CLI commands currently parse the template name and take that as a file location, but in practice it may be more helpful to have them accept a pre-parsed object in a process parallel to that of writing (e.g., the output could be YAML or HTML or whatever, but we don't handle that in the command).
This would make it easier for pre- and post-processing functions to know which template is currently being used since it will already be loaded, rather than isolated to a single CLI command.
The text was updated successfully, but these errors were encountered: