Feature requests

This one has been bugging me for a really long time. Whenever I work on a snippet, I can only see IF there are conditions associated with its exection, but I need to open the Condition Builder to see WHAT conditions are in place. I propose an improvement to the UI which lists the conditions which are in place for the current snippet without extra clicks. I have made a mock up of the UI to illustrate my idea. I have created two condition groups, each one consisting of two conditions but I am unsure if the proposed use of borders to indicate groups is intuitive enough. So, if you like the idea, please also comment on the visual implementation.

Backup & sync snippets to Dropbox or Google Drive.

As I personally transition from the Code Snippets plugin, one thing I'm finding that I'm missing is the ability to import/export snippets. This is important for ease of distribution to clients/customers that are not necessarily using WPCodeBox...yet. ; ) This goes hand in hand with the Add the ability to save CSS/JS to file feature request.

It would be helpful for users to see which cloud snippets are downloaded locally. A visual indication will be help with this.

Its pain to go trough every site and manually download updated snippets.

Possibility to create subfolders to hierarchize content or in any case tag system to find snippets more easily

Visual editor options to enhance the user experience. On small screens the three columns cause the space for the code editor to be quite small. Enable option to occupy the available layout width. Enable option to expand editor to full screen. Enable option to edit without distractions.

Revisions history would be very useful, especially for css. Also a trash folder, in order not to lose anything by mistake.

Ability to set condition to folder not separate scripts. Usecases: – Folder for slider (css+js) – Folder for set of tools or something related – User-related settings. For example, I'm doing some dev job right now together with another guy. He is in response of creating a them, but not to wait him to make everything done, I've added a bunch of draft styles to shop. Condition User=Me and now work comfortably with product catalog with good sidebar, product grid etc.

When creating a new snippet, use a template that you can define. This would be useful when adding a comment header to a PHP file for example: <?php /** Created by WPCodeBox. User: Ovidiu Date: 30.12.2021 Time: 17:58 */

In the code editor, there is an autocompletion for PHP and WP functions. But when selecting a function, there's no indication about parameters. For example, when I choose str_replace, it would be great to have something like this : str_replace(array|string $search, array|string $replace, string|array $subject, int &$count = null)

Please, you make community repository - where users can share own snippets to others users.

As described a bit in some other feedback, it seems like metadata and other things are still being stored in the db when using the Functionality Plugin. I think that it would be ideal if snippets/func plugin were decoupled as much as possible (ideally completely) from the database so as to reduce db calls. I think that relevant data could be stored in a sort of YAML format in a comment block, and then parsed in the background by WPCodeBox. It would also allow us to modify the metadata from our IDE, and probably also enable us to create snippets from the IDE as well.

When you have a folder selected, and click on "New Snippet" that snippet should ideally be created in the selected folder when you save it the first time.

It would be extremely useful to have a toggle that allows us to render the custom css also in the wordpress editor (Gutenberg). This way, when you write some css for a page in wpcodebox and then go modify that page in the editor, you can actually see the customized css.