fix: address temperature typo in LLMConfig class #1085
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
Simply fixing a typo ("temprature" vs "temperature") found in the LLMConfig class. These changes seek to align the spelling with what is generally expected in LiteLLM's documentation.
This would be a breaking API change because existing implementations would need to adopt the new spelling.
List of files changed and why
crawl4ai/async_configs.py
- To update the LLMConfig "temperature" constructor initializer and instance member spelling.crawl4ai/extraction_strategy.py
- Updating "temperature" spelling in the LLMExtractionStrategy docstring.deploy/docker/c4ai-code-context.md
- Updating the docker code-context file with the correct spelling. I was unsure if this was necessary as it seems this file is generated but was unable to find where/how it was generated. I am happy to remove this code change, just wanted to be thorough.How Has This Been Tested?
I was unable to get the other tests to run due to environmental issues, unrelated to the above code changes.
Checklist: