Allow GPT model to be configured via config file #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
This update introduces the capability for users to select the desired GPT model version via a configuration file. It moves away from the hardcoded GPT-3.5 model, enhancing flexibility and user control over model selection.
Changes:
config.example.json
), allowing users to specify their preferred model.config.example.json
to include a placeholder for the GPT model version.Motivation:
This change was motivated by the need to empower users with the flexibility to easily switch between different GPT models based on their requirements or the availability of newer models from OpenAI, without needing to alter the code.
Testing:
The feature was tested by specifying different GPT model versions in the
config.example.json
file. The application successfully utilized the specified models at runtime. Tests were conducted with GPT-3.5, GPT-4 (hypothetical future model), ensuring that the application behaves as expected across different model configurations.The test code has not been uploaded.