Project "group" property #451
-
Hi! This is possibly related to #50 Is the I assume this doesn't work yet. ...
{
"name": "Email Client Electron",
"rootPath": "C:\\xxx\\EmailClient\\electron",
"paths": [],
"group": "Email Client",
"enabled": true
},
{
"name": "Email Client Front-end",
"rootPath": "C:\\xxx\\EmailClient\\front-end",
"paths": [],
"group": "Email Client",
"enabled": true
},
{
"name": "Email Client backend",
"rootPath": "C:\\xxx\\EmailClient\\backend",
"paths": [],
"group": "Email Client",
"enabled": true
},
... |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @DejfCold , Yes, that On the other hand, the I'm planning to work on #50 soon, and will probably be a multi-release work. I'll update the issue with more details, once I start to work on it. Hope this helps |
Beta Was this translation helpful? Give feedback.
Hi @DejfCold ,
Yes, that
group
property is still not being used, and will be related to #50. In fact, I'm thinking about using another name, maybe tag or label, I'm not sure, mostly because there is a groupList setting which has no meaning to this. In the end, the idea is simple, be able to organize (treeview like) your projects by this group/tag/label.On the other hand, the
projectManager.groupList
setting group/organize the projects presented in theCommand Palette
, just to sort them in a way to present each kind of project separately.I'm planning to work on #50 soon, and will probably be a multi-release work. I'll update the issue with more details, once I start to work on it.
Hope t…