listen to more than one file in createFileSystemWatcher API

[Ramin-RX7]

I'm currently working on a vscode extension and need a file change detector. When using vscode.workspace.createFileSystemWatcher I can only specify one folder/file. I'm wondering if it is possible to add a function or change this function in a way that can accept more arguments for files we want to listen for changes.
(I know about glob patterns, but if folders/files have totally different paths, we need to make a complicated pattern for them or make several instances of createFileSystemWatcher with same behaviour. I'm asking if we can do this without a complicated pattern and without multiple instances)
(There are several different ways of doing this in my mind but I'll wait for your response.)
Related

[bpasero]

I do not understand the need here since you can easily call the method multiple times.

[vscodenpa]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[M-Zoldak]

I do not understand the need here since you can easily call the method multiple times.

I would really appreciate this feature. I'm using https://github.com/Natizyskunk/vscode-sftp where it's possible only to configure one watcher with glob pattern using function mentioned above.

On other side glob pattern supports writing multiple Files into pattern, which makes it in my opinion natural to configure it this way.

[theDyingMountain]

I can confirm the issue, glob pattern with multiple files are not useable.

[vscodenpa]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vscodenpa]

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!