feat: support glob patterns for project config#493
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the configuration flexibility for TypeScript projects by introducing glob pattern support in Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Pull request overview
Adds documented glob-pattern support for languageOptions.parserOptions.project so monorepo TypeScript config discovery can be maintained via patterns (including **) while working correctly with the configured VFS/overlay filesystem (e.g., LSP scenarios).
Changes:
- Expand glob patterns in
parserOptions.project, preserving user-specified entry order while deduplicating expanded paths. - Implement VFS-backed glob expansion via directory walking + doublestar matching (supports overlay VFS).
- Add focused tests covering glob expansion,
**, no-match errors, dedupe behavior, and overlay VFS behavior; update reporslint.jsonto use globs and ignoretypescript-go/**.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
internal/config/loader.go |
Adds glob detection/expansion and stable deduped path collection using the configured VFS. |
internal/config/loader_test.go |
Adds unit tests for glob expansion behavior and overlay VFS correctness. |
rslint.json |
Switches project configuration to glob patterns and restores typescript-go/** ignore. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
|
@kdy1 Hey! I took a look at the CI failure — here's what's going on: The glob patterns A simple fix would be to add |
|
@fansenze Thank you so much for the guidance! I did it :) |
Supersedes #439 with the remaining maintainer feedback applied on top of current
main.What changed:
languageOptions.parserOptions.project**, no-match, dedupe, and overlay VFS casesrslint.jsonto use package glob patterns and ignoretypescript-go/**Maintainer feedback addressed:
main// @ts-nocheckinpackages/rslint-wasm/src/worker.tstypescript-go/**Verification:
GOCACHE=/tmp/rslint-go-build go test ./internal/config -run 'Test(ContainsGlobPattern|LoadTsConfigsFromRslintConfig)'git diff --check -- internal/config/loader.go internal/config/loader_test.go rslint.json