How do I configure which folders to include/exclude to be used in the Quick Open search?
Current use case is to be able to open files in the extensions folder.
Bump. @patrick
Sorry to bug you on this @patrick, but unable to use quick open effectively without it serving all the files in the project.
I have to keep going in to the files manager to access public and extensions files.
Makes it hard to use the shortcut as part of development workflow.
Bump.
@George I see you have changed this to a FR. Not sure it had to be.
Can you please share the current folders criteria for the quick open search? Because it shows files from public folder in "recent" section, but does not actually search the public folder.
@patrick / @George Using this over the past couple of weeks, I see that it does search in the extensions and public folders.. it only fails when the search term contains a dot .
So if I search for custom
, it shows results, but custom.js
returns no results.
This is a bug in my opinion, but the primary request to configure folders still reamins.
The following folders are ignored in the Quick Open:
- .wappler
- .git
- .svn
- _notes
- lib
- node_modules
- dmxAppConnect
- dmxConnectLib
- dmxConnections
- bootstrap{4|5}
- fontawesome{4|5}
- framework7
- vendor
The recent files show all files recently opened in Wappler and ignores the above restriction. The folder restriction is only for the search to improve performance and excluding folders that normally don't contain any user files.
Thank you for the explanation.
Did you get a chance to check this:
For the search it ignores the file extension, will see if it would be logical to include that in the search, perhaps only for the custom files.
For a page named "payments" for example, server actions usually reside in a folder called payments. In order to open payments page, I have to manually scroll down to dynamic pages section to select the page.
If extension could be added for all files, this would be easier as well. I could just search for "ents.ej" to get to my page.