Skip to content

Raise per-package Go file cap from 200 to 2000 - #40

Open
bad33ndj3 wants to merge 1 commit into
mainfrom
fix/package-file-cap
Open

Raise per-package Go file cap from 200 to 2000#40
bad33ndj3 wants to merge 1 commit into
mainfrom
fix/package-file-cap

Conversation

@bad33ndj3

Copy link
Copy Markdown
Owner

Summary

  • listPackageFiles threw "Package … contains too many Go files" for any package directory with over 200 .go files, blocking hover/go-to-definition on large packages.
  • The cap was a flat preflight check, not a real limit: downloads (mapLimit, concurrency 6) and worker indexing already happen incrementally, so nothing in the pipeline actually needs a low ceiling.
  • Raised the cap to 2000 as a sanity ceiling against truly pathological directories, while letting normal large packages load.

Test plan

  • npm run check:syntax
  • npm test (577/577)

🤖 Generated with Claude Code

https://claude.ai/code/session_01NbVVA6kUeVF2Kx8FJJVMsj

Downloads and indexing already happen incrementally (mapLimit
concurrency 6 in source-loader.js), so the flat 200-file preflight
throw in listPackageFiles was an overly conservative guard, not a
real technical ceiling.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NbVVA6kUeVF2Kx8FJJVMsj
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.

1 participant