You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the sounds package I would like the sound files to be output directly into the sounds directory, instead of sounds/Sounds. I have a few other things in this vein that I would like to accomplish. but guidance on how to accomplish this task should suffice.
Do you have any ideas on how I can modify this?
The text was updated successfully, but these errors were encountered:
If I understand this correctly, it would also require changes to the client-side of things.
All package assets are put into their own base directory so that everything is isolated. If the target directory is below this, it would open up the chances of packages overriding files with similar names.
Do you have an idea of where I would start? It looks like client/src/adapters/vfs/apps.js is what I will need to modify on the client, but I'm not sure what the best approach from there is and whether or not I need to change anything within the actual CLI package
Sounds good, no real rush. And my use case is I created a static-wallpapers package to offer the users a predefined selection of wallpaper images to choose from as the starting directory when opening the wallpaper file dialog, and currently the directory is wallpapers/Wallpapers and I'd like to avoid the nesting if possible for a cleaner experience
For the
sounds
package I would like the sound files to be output directly into thesounds
directory, instead ofsounds/Sounds
. I have a few other things in this vein that I would like to accomplish. but guidance on how to accomplish this task should suffice.Do you have any ideas on how I can modify this?
The text was updated successfully, but these errors were encountered: