summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--CONTRIBUTING.md2
-rw-r--r--continuedev/README.md2
-rw-r--r--continuedev/notes.md2
-rw-r--r--continuedev/src/continuedev/core/autopilot.py4
-rw-r--r--continuedev/src/continuedev/libs/constants/default_config.py2
-rw-r--r--continuedev/src/continuedev/libs/llm/__init__.py4
-rw-r--r--continuedev/src/continuedev/libs/util/copy_codebase.py2
-rw-r--r--continuedev/src/continuedev/models/filesystem.py2
-rw-r--r--continuedev/src/continuedev/models/main.py2
-rw-r--r--continuedev/src/continuedev/plugins/policies/default.py2
-rw-r--r--continuedev/src/continuedev/plugins/recipes/AddTransformRecipe/steps.py2
-rw-r--r--continuedev/src/continuedev/plugins/recipes/ContinueRecipeRecipe/main.py2
-rw-r--r--continuedev/src/continuedev/plugins/recipes/TemplateRecipe/main.py2
-rw-r--r--continuedev/src/continuedev/plugins/steps/main.py2
-rw-r--r--continuedev/src/continuedev/plugins/steps/search_directory.py2
-rw-r--r--continuedev/src/continuedev/server/ide.py2
-rw-r--r--docs/docs/how-to-use-continue.md2
-rw-r--r--docs/docs/walkthroughs/create-a-recipe.md2
-rw-r--r--docs/docs/walkthroughs/use-the-gui.md4
-rw-r--r--extension/README.md2
-rw-r--r--extension/esbuild.test.mjs2
-rw-r--r--extension/src/activation/activate.ts4
22 files changed, 26 insertions, 26 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d0ea7556..21f5e970 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -66,7 +66,7 @@ VSCode is assumed for development as Continue is primarily a VSCode tool at the
3. Hit play button
4. This will start both the server and the extension in debug mode and open a new VSCode window with continue extension
1. I call the VSCode window with the extension the *Host VSCode*
- 2. The window you started debugging from is reffered to as the *Main VSCode*
+ 2. The window you started debugging from is referred to as the *Main VSCode*
5. Notice 2 debug sessions are running, one for the server and one for the extension, you can also set breakpoints in both
4. Lets try using breakpoints:
diff --git a/continuedev/README.md b/continuedev/README.md
index 6a11ae43..542274b5 100644
--- a/continuedev/README.md
+++ b/continuedev/README.md
@@ -69,7 +69,7 @@ cd continue/extension/scripts && python3 install_from_source.py
- [Continue Server README](./README.md): learn about the core of Continue, which can be downloaded as a [PyPI package](https://pypi.org/project/continuedev/)
- [VS Code Extension README](../extension/README.md): learn about the capabilities of our extension—the first implementation of Continue's IDE Protocol—which makes it possible to use use Continue in VS Code and GitHub Codespaces
-- [Continue GUI README](../extension/react-app/): learn about the React app that lets users interact with the server and is placed adjacent to the text editor in any suppported IDE
+- [Continue GUI README](../extension/react-app/): learn about the React app that lets users interact with the server and is placed adjacent to the text editor in any supported IDE
- [Schema README](../schema/README.md): learn about the JSON Schema types generated from Pydantic models, which we use across the `continuedev/` and `extension/` directories
- [Continue Docs README](../docs/README.md): learn how our [docs](https://continue.dev/docs) are written and built
- [How to debug the VS Code Extension README](../extension/src/README.md): learn how to set up the VS Code extension, so you can debug it
diff --git a/continuedev/notes.md b/continuedev/notes.md
index bfd8cf4a..469d4950 100644
--- a/continuedev/notes.md
+++ b/continuedev/notes.md
@@ -25,7 +25,7 @@ There should be different levels of abstraction at which you can work with these
---
- One big thing that happens as you're fixing errors is that you encounter a fork in the road. The language model should be able to present you with both options, and you just click to decide.
-- What I'm doing right now: I write a bunch of code without running it, then ahve to solve a bunch of errors at once, but small obvious ones. We can do this all automatically.
+- What I'm doing right now: I write a bunch of code without running it, then have to solve a bunch of errors at once, but small obvious ones. We can do this all automatically.
---
diff --git a/continuedev/src/continuedev/core/autopilot.py b/continuedev/src/continuedev/core/autopilot.py
index f24f5ad7..a27b0cb7 100644
--- a/continuedev/src/continuedev/core/autopilot.py
+++ b/continuedev/src/continuedev/core/autopilot.py
@@ -251,9 +251,9 @@ class Autopilot(ContinueBaseModel):
def handle_manual_edits(self, edits: List[FileEditWithFullContents]):
for edit in edits:
self._manual_edits_buffer.append(edit)
- # TODO: You're storing a lot of unecessary data here. Can compress into EditDiffs on the spot, and merge.
+ # TODO: You're storing a lot of unnecessary data here. Can compress into EditDiffs on the spot, and merge.
# self._manual_edits_buffer = merge_file_edit(self._manual_edits_buffer, edit)
- # Note that this is being overriden to do nothing in DemoAgent
+ # Note that this is being overridden to do nothing in DemoAgent
async def handle_command_output(self, output: str):
get_traceback_funcs = [get_python_traceback, get_javascript_traceback]
diff --git a/continuedev/src/continuedev/libs/constants/default_config.py b/continuedev/src/continuedev/libs/constants/default_config.py
index c197680d..d93dffcd 100644
--- a/continuedev/src/continuedev/libs/constants/default_config.py
+++ b/continuedev/src/continuedev/libs/constants/default_config.py
@@ -33,7 +33,7 @@ config = ContinueConfig(
custom_commands=[
CustomCommand(
name="test",
- description="Write unit tests for the higlighted code",
+ description="Write unit tests for the highlighted code",
prompt="Write a comprehensive set of unit tests for the selected code. It should setup, run tests that check for correctness including important edge cases, and teardown. Ensure that the tests are complete and sophisticated. Give the tests just as chat output, don't edit any file.",
)
],
diff --git a/continuedev/src/continuedev/libs/llm/__init__.py b/continuedev/src/continuedev/libs/llm/__init__.py
index ac4742c7..baeb9d1a 100644
--- a/continuedev/src/continuedev/libs/llm/__init__.py
+++ b/continuedev/src/continuedev/libs/llm/__init__.py
@@ -86,7 +86,7 @@ class LLM(ContinueBaseModel):
template_messages: Optional[Callable[[List[Dict[str, str]]], str]] = Field(
None,
- description="A function that takes a list of messages and returns a prompt. This ensures that models like llama2, which are trained on specific chat formats, will always recieve input in that format.",
+ description="A function that takes a list of messages and returns a prompt. This ensures that models like llama2, which are trained on specific chat formats, will always receive input in that format.",
)
write_log: Optional[Callable[[str], None]] = Field(
None,
@@ -121,7 +121,7 @@ class LLM(ContinueBaseModel):
"description": 'A dictionary of prompt templates that can be used to customize the behavior of the LLM in certain situations. For example, set the "edit" key in order to change the prompt that is used for the /edit slash command. Each value in the dictionary is a string templated in mustache syntax, and filled in at runtime with the variables specific to the situation. See the documentation for more information.'
},
"template_messages": {
- "description": "A function that takes a list of messages and returns a prompt. This ensures that models like llama2, which are trained on specific chat formats, will always recieve input in that format."
+ "description": "A function that takes a list of messages and returns a prompt. This ensures that models like llama2, which are trained on specific chat formats, will always receive input in that format."
},
"write_log": {
"description": "A function that is called upon every prompt and completion, by default to log to the file which can be viewed by clicking on the magnifying glass."
diff --git a/continuedev/src/continuedev/libs/util/copy_codebase.py b/continuedev/src/continuedev/libs/util/copy_codebase.py
index aafb435c..78f38148 100644
--- a/continuedev/src/continuedev/libs/util/copy_codebase.py
+++ b/continuedev/src/continuedev/libs/util/copy_codebase.py
@@ -67,7 +67,7 @@ class CopyCodebaseEventHandler(PatternMatchingEventHandler):
# It should be the autopilot that makes the update right? It's just another action, everything comes from a single stream.
def _event_to_edit(self, event) -> Union[FileSystemEdit, None]:
- # NOTE: You'll need to map paths to create both an action within the copy filesystem (the one you take) and one in the original fileystem (the one you'll record and allow the user to accept). Basically just need a converter built in to the FileSystemEdit class
+ # NOTE: You'll need to map paths to create both an action within the copy filesystem (the one you take) and one in the original filesystem (the one you'll record and allow the user to accept). Basically just need a converter built in to the FileSystemEdit class
src = event.src_path()
if event.is_directory:
if event.event_type == "moved":
diff --git a/continuedev/src/continuedev/models/filesystem.py b/continuedev/src/continuedev/models/filesystem.py
index 514337bf..3b056a2f 100644
--- a/continuedev/src/continuedev/models/filesystem.py
+++ b/continuedev/src/continuedev/models/filesystem.py
@@ -371,7 +371,7 @@ class VirtualFileSystem(FileSystem):
raise NotImplementedError
def add_directory(self, path: str):
- # For reasons as seen here and in delete_directory, a Dict[str, str] might not be the best represntation. Could just preprocess to something better upon __init__
+ # For reasons as seen here and in delete_directory, a Dict[str, str] might not be the best representation. Could just preprocess to something better upon __init__
pass
def apply_file_edit(self, edit: FileEdit) -> EditDiff:
diff --git a/continuedev/src/continuedev/models/main.py b/continuedev/src/continuedev/models/main.py
index a8b4aab0..880fbfef 100644
--- a/continuedev/src/continuedev/models/main.py
+++ b/continuedev/src/continuedev/models/main.py
@@ -82,7 +82,7 @@ class Range(BaseModel):
return self.start == self.end
def indices_in_string(self, string: str) -> Tuple[int, int]:
- """Get the start and end indicees of this range in the string"""
+ """Get the start and end indices of this range in the string"""
lines = string.splitlines()
if len(lines) == 0:
return (0, 0)
diff --git a/continuedev/src/continuedev/plugins/policies/default.py b/continuedev/src/continuedev/plugins/policies/default.py
index 2c9c3d9c..85d8c528 100644
--- a/continuedev/src/continuedev/plugins/policies/default.py
+++ b/continuedev/src/continuedev/plugins/policies/default.py
@@ -57,7 +57,7 @@ class DefaultPolicy(Policy):
default_params: dict = {}
def next(self, config: ContinueConfig, history: History) -> Step:
- # At the very start, run initial Steps spcecified in the config
+ # At the very start, run initial Steps specified in the config
if history.get_current() is None:
shown_welcome_file = os.path.join(getServerFolderPath(), ".shown_welcome")
if os.path.exists(shown_welcome_file):
diff --git a/continuedev/src/continuedev/plugins/recipes/AddTransformRecipe/steps.py b/continuedev/src/continuedev/plugins/recipes/AddTransformRecipe/steps.py
index 0091af97..c7e60f12 100644
--- a/continuedev/src/continuedev/plugins/recipes/AddTransformRecipe/steps.py
+++ b/continuedev/src/continuedev/plugins/recipes/AddTransformRecipe/steps.py
@@ -80,7 +80,7 @@ class AddTransformStep(Step):
{dlt_transform_docs}"""
)
- # edit the pipeline to add a tranform function and attach it to a resource
+ # edit the pipeline to add a transform function and attach it to a resource
await sdk.edit_file(
filename=filename,
prompt=prompt,
diff --git a/continuedev/src/continuedev/plugins/recipes/ContinueRecipeRecipe/main.py b/continuedev/src/continuedev/plugins/recipes/ContinueRecipeRecipe/main.py
index e67ea557..3dff2e15 100644
--- a/continuedev/src/continuedev/plugins/recipes/ContinueRecipeRecipe/main.py
+++ b/continuedev/src/continuedev/plugins/recipes/ContinueRecipeRecipe/main.py
@@ -33,7 +33,7 @@ class ContinueStepStep(Step):
Please edit the code to write your own Step that does the following:
- {self.prommpt}
+ {self.prompt}
It should be a subclass of Step as above, implementing the `run` method, and using pydantic attributes to define the parameters.
diff --git a/continuedev/src/continuedev/plugins/recipes/TemplateRecipe/main.py b/continuedev/src/continuedev/plugins/recipes/TemplateRecipe/main.py
index 2ca65b8e..01ae364d 100644
--- a/continuedev/src/continuedev/plugins/recipes/TemplateRecipe/main.py
+++ b/continuedev/src/continuedev/plugins/recipes/TemplateRecipe/main.py
@@ -10,7 +10,7 @@ class TemplateRecipe(Step):
Use this as a template to create your own!
"""
- # Paremeters for the recipe
+ # Parameters for the recipe
name: str
# A title for the recipe, to be displayed in the GUI
diff --git a/continuedev/src/continuedev/plugins/steps/main.py b/continuedev/src/continuedev/plugins/steps/main.py
index 1c8638ec..43299d00 100644
--- a/continuedev/src/continuedev/plugins/steps/main.py
+++ b/continuedev/src/continuedev/plugins/steps/main.py
@@ -47,7 +47,7 @@ class FasterEditHighlightedCodeStep(Step):
REPLACE_WITH
<CODE_TO_REPLACE_WITH>
- where <CODE_TO_REPLACE> and <CODE_TO_REPLACE_WITH> can be multiple lines, but should be the mininum needed to make the edit. Be sure to maintain existing whitespace at the start of lines.
+ where <CODE_TO_REPLACE> and <CODE_TO_REPLACE_WITH> can be multiple lines, but should be the minimum needed to make the edit. Be sure to maintain existing whitespace at the start of lines.
For example, if you want to replace the code `x = 1` with `x = 2` in main.py, you would write:
FILEPATH
diff --git a/continuedev/src/continuedev/plugins/steps/search_directory.py b/continuedev/src/continuedev/plugins/steps/search_directory.py
index 04fb98b7..7ca8a2be 100644
--- a/continuedev/src/continuedev/plugins/steps/search_directory.py
+++ b/continuedev/src/continuedev/plugins/steps/search_directory.py
@@ -25,7 +25,7 @@ def find_all_matches_in_dir(pattern: str, dirpath: str) -> List[RangeInFile]:
if file in IGNORE_FILES:
continue # pun intended
with open(os.path.join(root, file), "r") as f:
- # Find the index of all occurences of the pattern in the file. Use re.
+ # Find the index of all occurrences of the pattern in the file. Use re.
file_content = f.read()
results = re.finditer(pattern, file_content)
range_in_files += [
diff --git a/continuedev/src/continuedev/server/ide.py b/continuedev/src/continuedev/server/ide.py
index bdb5817d..7396b1db 100644
--- a/continuedev/src/continuedev/server/ide.py
+++ b/continuedev/src/continuedev/server/ide.py
@@ -358,7 +358,7 @@ class IdeProtocolServer(AbstractIdeProtocolServer):
pass
def onCloseGUI(self, session_id: str):
- # Accesss to SessionManager
+ # Access to SessionManager
pass
def onOpenGUIRequest(self):
diff --git a/docs/docs/how-to-use-continue.md b/docs/docs/how-to-use-continue.md
index bf61a033..3f21d92c 100644
--- a/docs/docs/how-to-use-continue.md
+++ b/docs/docs/how-to-use-continue.md
@@ -12,7 +12,7 @@ As you use Continue more, you will learn when to trust it. A great way to get st
If you are trying to use it for a new task and don’t have a sense of how much Continue can help you complete it, it can often be helpful to start like this:
-1. Highlight the code section(s) that you don’t understand and type "tell me how this code works" in the intput box
+1. Highlight the code section(s) that you don’t understand and type "tell me how this code works" in the input box
2. If the explanation seems reasonable, then, while still highlighting the code section(s), type "how would you change this code to [INSERT TASK]?"
3. If this explanation is also pretty good, then, while still highlighting the code section(s), type `/edit [INSERT TASK]`
4. If it does not work on first attempt, click `reject` on its suggestions and try again—often it will make a different suggestion each time
diff --git a/docs/docs/walkthroughs/create-a-recipe.md b/docs/docs/walkthroughs/create-a-recipe.md
index 2cb28f77..3ec641c6 100644
--- a/docs/docs/walkthroughs/create-a-recipe.md
+++ b/docs/docs/walkthroughs/create-a-recipe.md
@@ -54,7 +54,7 @@ class CreatePipelineRecipe(Step):
### Using the SDK
-You will want to use the SDK when you are opening directories, editing files, using models, etc. This will ensure that these actions are recorded as steps, so they are reviewable, reversable, and rerunnable.
+You will want to use the SDK when you are opening directories, editing files, using models, etc. This will ensure that these actions are recorded as steps, so they are reviewable, reversible, and rerunnable.
### Allow for configurability
diff --git a/docs/docs/walkthroughs/use-the-gui.md b/docs/docs/walkthroughs/use-the-gui.md
index 055150c7..33bc3b62 100644
--- a/docs/docs/walkthroughs/use-the-gui.md
+++ b/docs/docs/walkthroughs/use-the-gui.md
@@ -8,7 +8,7 @@
3. Press the `Continue` button
-4. Review the explaination of what was edited and why on the Continue GUI
+4. Review the explanation of what was edited and why on the Continue GUI
5. Check the code that was edited by the LLM in the code editor
@@ -22,7 +22,7 @@ Context is not carried across steps at the moment, so you will need to repeat an
## Review actions taken
-Whether you are using a recipe or not, you will want to review the explainations of what the LLM did and check the code that it generated. You are ultimately responsible for any code that you ship, even if it was written by a LLM.
+Whether you are using a recipe or not, you will want to review the explanations of what the LLM did and check the code that it generated. You are ultimately responsible for any code that you ship, even if it was written by a LLM.
## Reverse button
diff --git a/extension/README.md b/extension/README.md
index e11fd2d9..8c4d1d6c 100644
--- a/extension/README.md
+++ b/extension/README.md
@@ -21,7 +21,7 @@
## Task, not tab, auto-complete
-### Get possible explainations
+### Get possible explanations
Ask Continue about a part of your code to get another perspective
diff --git a/extension/esbuild.test.mjs b/extension/esbuild.test.mjs
index fdffd3da..f6dc092c 100644
--- a/extension/esbuild.test.mjs
+++ b/extension/esbuild.test.mjs
@@ -10,7 +10,7 @@ import glob from "glob";
// Bundles script to run tests on VSCode host + mocha runner that will be invoked from within VSCode host
await esbuild.build({
entryPoints: [
- // Runs mocha runner on VSCode host usig runTests from @vscode/test-electron
+ // Runs mocha runner on VSCode host using runTests from @vscode/test-electron
"src/test-runner/runTestOnVSCodeHost.ts",
// Runs the bundled tests using Mocha class
diff --git a/extension/src/activation/activate.ts b/extension/src/activation/activate.ts
index de7464bf..7481c211 100644
--- a/extension/src/activation/activate.ts
+++ b/extension/src/activation/activate.ts
@@ -34,7 +34,7 @@ export async function activateExtension(context: vscode.ExtensionContext) {
console.log("Error getting workspace folder: ", e);
}
// Before anything else, check whether this is an out-of-date version of the extension
- // Do so by grabbing the package.json off of the GitHub respository for now.
+ // Do so by grabbing the package.json off of the GitHub repository for now.
fetch(PACKAGE_JSON_RAW_GITHUB_URL)
.then(async (res) => res.json())
.then((packageJson) => {
@@ -81,7 +81,7 @@ export async function activateExtension(context: vscode.ExtensionContext) {
return await ideProtocolClient.getSessionId();
})();
- // Register Continue GUI as sidebar webview, and beging a new session
+ // Register Continue GUI as sidebar webview, and beginning a new session
const provider = new ContinueGUIWebviewViewProvider(sessionIdPromise);
context.subscriptions.push(