When conducting peer code reviews, fill out the template below in a comment on your peer’s pull request.

# Peer Code Review

## Correctness

The code satisfies the requirements outlined in the project description. Check the box for each requirement that is satisfied (as shown by the images and code changes in the Pull Request):
- [ ] Requirement 1: Show the user their current line number when the Go To Line popup is displayed. See the image of the VSCode feature to see an example.
- [ ] Requirement 2: If the user enters a value that is too large (bigger than the total number of lines), a red error message should be shown to users that says `Enter a number between 1 and N, inclusive where N is the number of lines in the file`.
- [ ] Requirement 3: Implement the logic for handling a negative number using reverse indexing. For example, -1 should go to the last line, -2 should be the second to last line, etc. If a user enters a number that is too negative such that it extends past the first line, the error message shown to users should say `Negative entries must be between -N and -1, inclusive where N is the number of lines in the file`.
- [ ] Requirement 4: Change the Go To Line popup such that the popup should show the user the range of values allowed (i.e., show the total number of lines). You can choose the exact wording, but it should mention that a user can enter a number between 1 and N or -N and -1.
- [ ] (Optional) Requirement 5: Allow entries for the Go To Line popup to be formatted like X:Y where X is the line number and Y is the column (character) number within that line.

## Simple Design

The design of the solution should focus on simplicity, clarity, and maintainability. Students should evaluate whether the code adheres to these principles:
- [ ] Exemplary: The design is easy to understand, modular, and avoids unnecessary complexity. It follows established design principles such as separation of concerns and single responsibility. Functions and classes are appropriately sized, and the logic is straightforward and efficient.
- [ ] Satisfactory: The design is mostly clear and functional but may include minor complexities or redundancies that could be simplified. Some opportunities for better modularization or adherence to design principles exist.
- [ ] Needs Improvement: The design is difficult to follow or overly complex. There are clear violations of design principles, such as tightly coupled components or overly large functions/classes.
- [ ] Missing or None: The design lacks structure or is so poorly implemented that it cannot be reasonably understood or maintained.


### Explain your choice:

Discuss in your answer the following:
- Are functions/classes too large or trying to do too much?
- Are there unnecessary dependencies or overly complex logic?
- Is the code easy to follow for someone new to the project?

*insert your answer here*

## Code Style

Code style focuses on readability, consistency, and adherence to coding standards. Students should evaluate whether the code meets these criteria (check one):
- [ ] Exemplary: The code strictly follows established coding conventions (e.g., naming conventions, indentation, spacing). It is well-documented with comments where necessary and variable/function names are descriptive. The formatting is clean and consistent throughout.
- [ ] Satisfactory: The code mostly adheres to coding standards but may have minor inconsistencies in formatting or naming conventions. Comments are present but could be more detailed or better placed.
- [ ] Needs Improvement: The code has significant style issues, such as inconsistent formatting, unclear naming conventions, or insufficient documentation. These issues negatively impact readability.
- [ ] Missing or None: The code does not follow any recognizable style guide. It is poorly formatted, lacks meaningful comments, and uses unclear or inconsistent names.

### Explain your choice:

Discuss in your answer the following:
- Are variable/function names descriptive and consistent?
- Is the code properly indented and formatted?
- Are comments used effectively to explain non-obvious logic?
- Does the code follow the project's style guide?

*insert your answer here*

## Would you merge this PR?

*insert your answer here*