Hi, Does anyone know what file structure the Webs...
# sdf
n
Hi, Does anyone know what file structure the Webstorm plugin is dependant on? We’re trying out a setup where we in a Webstorm project have multiple SDF projects instead of one. So instead of: Project / src / FileCabinet / SuiteScripts .. etc We want to do: Project / Solution1 / src / FileCabinet / SuiteScripts / Solution1 .. etc Project / Solution2 / src / FileCabinet / SuiteScripts / Solution2 .. etc But when we use that structure the plugin stops working (inactive/grayed out) when for example right clicking a file in Project / Solution2 / src / FileCabinet / SuiteScripts / Solution2 to compare it with the account version. We’ve tried playing around with the defaultProjectFolder attribute in the suitecloud.config.js but it’s not really working. Has anyone tried this kind of setup? Can the plugin be configured in some other way?
c
If you're on a mac or linux you'll be able to fudge this with symbolic links
n
Unfortunately we have a mix of Mac and PC users so we’d need a more generic solution.. but what do you mean in the case of Unix systems and symbolic links, what links would you create aliases for?
Update: Got the plugin working, unfortunately by adding a deployment/manifest file to the top level folder. When deploying (no matter what file/folder you use to trigger the deploy) it will use that top level deployment file instead of the one corresponding to the sub-project 😕
🤔 1
m
It's not quite ready yet but I've done some work on a VS Code extension that adds support for multi-projects like this
n
@michoel thanks! I’ll have a look
My NetSuite VS Code plugin I am alpha testing does this, but feedback was this was not useful.
m
@chris from what I can understand the feedback was that users didn't want to have a separate copy of the project for each environment
but the ability to have multiple SDF projects in a single project is something that I believe us highly useful
c
🥲
We could probably do both and move it all to settings files
I found it incredibly useful
However, it is a lot of noise for most users with single instance setups
m
The extension I shared is intended to work together with the official extension to add multi-project and multi-user support
👏 2
@netsuite_insights did some work to improve it, specifically to cater for the use case of multiple customers. Hopefully will publish it in the marketplace in the near future, it just needs some final touches
👏 1
💯 1
c
I’m working backwards from the user and going to the plug-in.. my goal is to support broader NodeJS/backend operations and asynchronous package builds
To that end I can’t really support the official plugin, but I can support the official node SDK