Refactor/organize root files#80
Conversation
…/typescript/ Split tree_parser/ by language domain: Rust parsers go to parser/rust/, TypeScript/JS parsers go to parser/typescript/. Rename file_processor to pipeline to reflect its role in the data flow. Backward-compatible re-exports in lib.rs keep all tests passing without changes.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request refactors the internal module structure of the LSP server, organizing source files into more structured directories such as discovery, parser (with rust and typescript submodules), and pipeline. It also updates imports and sets up backward-compatible aliases in lib.rs. However, a compilation issue was identified in lsp-server/src/main.rs because moving scanner inside the discovery module breaks absolute path references like crate::scanner in other submodules. Re-exporting scanner at the root using pub(crate) use will resolve this compilation error.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| mod utils; | ||
|
|
||
| use crate::discovery::config_reader; | ||
| use crate::discovery::scanner; |
There was a problem hiding this comment.
The submodule lsp-server/src/discovery/config_reader.rs references crate::scanner::find_tauri_config using an absolute path. Since scanner was moved inside the discovery module and is no longer declared as a root module in main.rs, compiling the binary crate will fail because crate::scanner cannot be resolved.
Changing this import to pub(crate) use re-exports scanner at the root of the binary crate, resolving the compilation error.
pub(crate) use crate::discovery::scanner;1 participant
No description provided.