Skip to content

Conversation

@Faanbaria
Copy link
Contributor

@Faanbaria Faanbaria commented Nov 25, 2025

When endLine exceeds the actual file length, ReadFileTool throws an error like "endLine=200 must be <= lineCount=50 or -1". Instead of failing, it should return all available lines with a warning.

https://youtrack.jetbrains.com/issue/KG-534

Type of the changes

  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Tests improvement
  • Refactoring

Checklist

  • The pull request has a description of the proposed change
  • I read the Contributing Guidelines before opening the pull request
  • The pull request uses develop as the base branch
  • Tests for the changes have been added
  • All new and existing tests passed
Additional steps for pull requests adding a new feature
  • An issue describing the proposed change exists
  • The pull request includes a link to the issue
  • The change was discussed and approved in the issue
  • Docs have been added / updated

@github-actions
Copy link

Qodana for JVM

1131 new problems were found

Inspection name Severity Problems
Check Kotlin and Java source code coverage 🔶 Warning 1120
Missing KDoc for public API declaration 🔶 Warning 11
@@ Code coverage @@
+ 72% total lines covered
16630 lines analyzed, 12065 lines covered
# Calculated according to the filters of your coverage tool

☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

public data class Result(val file: FileSystemEntry.File) : ToolResult.TextSerializable() {
public data class Result(
val file: FileSystemEntry.File,
internal val warningMessage: String? = null
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally it looks a bit weird when public data class has non-public fields. I see no reason to make it internal here, let's remove internal?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants