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
{{ message }}
This repository has been archived by the owner on Jul 31, 2023. It is now read-only.
In workspace settings, turn on filewatcher, set up your auth token, turn on notifications.
Add one folder to the workspace, let's call this the "bitburn" folder.
Create a folder inside the "bitburn folder" called the "bbscripts" folder.
Set your "bitburner script root" in the extension to: "./bbscripts/"
Observe that your scripts in the "bbscripts" folder upload successfully on save.
In vscode go to "file, add folder to workspace"
Add your eslint-plugin-bitburning folder (a project I'm working on ;) ) to your workspace
Exit vscode
Open vscode
Observe that changes to scripts in the "bbscripts" folder are no longer synched
I understand that it won't be supported to synch multiple folders in. But that's not what I want. Hoping for a way to specify that only the "bitburn" workspace folder is synched with the plugin, while still being able to have the "eslint-plugin-bitburning" folder open.
I attempted to workaround this by using folder level settings, but folder level settings didn't seem to work at all, it wouldn't even load the filewatcher for example.
same issue. I've set up my workspace with 3 places, but it not working with no success or error messages. But if i open the directory, not workspace, it's syncing brilliant.
I've checked paths and token, everything is ok: the full path is visible on start and it's correct.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
To reproduce:
eslint-plugin-bitburning
folder (a project I'm working on ;) ) to your workspaceI understand that it won't be supported to synch multiple folders in. But that's not what I want. Hoping for a way to specify that only the "bitburn" workspace folder is synched with the plugin, while still being able to have the "eslint-plugin-bitburning" folder open.
I attempted to workaround this by using folder level settings, but folder level settings didn't seem to work at all, it wouldn't even load the filewatcher for example.
Discord references:
https://discord.com/channels/415207508303544321/923428435618058311/931380461354254346
https://discord.com/channels/415207508303544321/923428435618058311/931379041171296256
The text was updated successfully, but these errors were encountered: