refactor: Update models and client to use new ReadSourceCodeRequest

[maks-ivanov]

CodeAnt-AI Description

• Refactored the lsproxy client to use the new ReadSourceCodeRequest instead of FileRange for reading source code.
• Introduced a new Range class and refactored FileRange to incorporate it.
• Added a new ReadSourceCodeRequest class to the models.
• Updated version numbers in __init__.py and pyproject.toml to reflect the changes.
• Removed unused imports and simplified code in lsproxy/modal.py.

---

Changes walkthrough

	Relevant files
Configuration changes	__init__.py Update version number in init file                                                          lsproxy/init.py Updated the version number from 0.2.0 to 0.3.0. +1/-1      pyproject.toml Update project version in pyproject.toml                                              pyproject.toml Updated project version from 0.2.5 to 0.3.0. +1/-1
Enhancement	client.py Refactor client to use ReadSourceCodeRequest                                      lsproxy/client.py Replaced FileRange with ReadSourceCodeRequest in read_source_code method. Updated docstring for read_source_code method. Updated default version in initialize_with_modal method. +14/-6    modal.py Clean up imports and simplify exec command                                          lsproxy/modal.py Removed unused import json. Simplified exec command for starting lsproxy. +1/-2      models.py Refactor models and add ReadSourceCodeRequest                                    lsproxy/models.py Introduced Range class for start and end positions. Refactored FileRange to use Range. Added ReadSourceCodeRequest class. Removed include_declaration field from GetReferencesRequest. +27/-18

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

Pull Request Feedback 🔍

🔒 No security issues identified

⚡ Recommended areas for review Type Check Ensure that the type check for ReadSourceCodeRequest is necessary and correctly implemented. Code Smell Consider whether the Range class should be a nested class within FileRange for better encapsulation.

[codeant-ai]

Suggestion: Consider checking if the request.model_dump() returns a valid JSON object before passing it to the _request method to avoid potential runtime errors. [possible issue]

Suggested change

	response = self._request(
	"POST", "/workspace/read-source-code", json=request.model_dump()
	json_data = request.model_dump()
	if not isinstance(json_data, dict):
	raise ValueError("Invalid JSON data")
	response = self._request(
	"POST", "/workspace/read-source-code", json=json_data
	)

[codeant-ai]

Suggestion: Ensure that the self.sandbox.exec("lsproxy") command is checked for successful execution to handle any potential errors during the process. [possible issue]

Suggested change

	self.sandbox.exec("lsproxy")
	result = self.sandbox.exec("lsproxy")
	if result.failed:
	raise RuntimeError("Failed to start lsproxy")

[robmck1995]

LGTM