Added support for the language model gptTurbo0301, and updated the Readme file #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…model, and updated the Readme file to include instructions for the .env file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I noticed that the app only used the text-davinci language model and that the version of the chat_gpt_skd was too old. There, I updated the package to the last version, and I added a method to the ChatScreen class to specify the model as an argument passed to it along with the message or the prompt, and accordingly, it sends the request and receives the response. Meaning, you can choose the model to be text-davinci, gptTurbo0301, or whatever you need when calling the '_chooseModel' method. Besides, I noticed that no instructions were provided about the '.env' file, and not all Flutter devs are familiar with it, so I updated the 'Readme' file to include instructions on how to set the API key in the '.env' file.