Basic per-folder config system #40
Conversation
| try { | ||
| //const content = fs.readFileSync(configPath, { encoding: "utf-8" }); | ||
| //const parsedContent = JSON.parse(content); | ||
| fs.writeFileSync(configPath, JSON.stringify(c, undefined, 4)); |
There was a problem hiding this comment.
JSON indentation should follow VScode settings. Will fix.
|
@GreenXenith If you validate the concept I will start making the extension use this. |
@AFCMS Concept is good 👍 |
(WIP non fonctionning code)
|
I have literally more than 30 files modified in my workspace currently, so I may push known non-working/partial changes. |
Some properties defined in the config schema aren't used yet
|
@GreenXenith I made quite a few changes unrelated to the title of the PR (because refactoring file structure is really painful). Could you give them a look? It should even work locally. I added a template system for both game and mod (modpack, mod in game, modpack in game are still to be done) They support multiple workspace folders. I also added an option to automatically initialize a Git repository when creating a template. My plan is also to optionally set the I think its OK to depend on the Git extension since its builtin in vscode/vscodium. |
- Website - ContentDB - GitHub - Forums
|
I added a basic #44 implementation. Still need a few more links. |
@GreenXenith
Basic per folder config system.
Partial fix for #35
EDIT: Fixed
Still lacks JSON schema validation since only one feature is present in the file yet.