Is there anyway to specify custom asconfig.json path? #778
-
Hi! I don't want to place asconfig.json at the root as it always gets pushed to the bottom of the folder. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Similar to TypeScript's tsconfig.json, asconfig.json is intended to be placed at the root of the project, and not in a sub-directory. vscode-as3mxml can detect asconfig.json files in sub-directories, and it treats each one as a separate project. However, when asconfig.json is in a sub-directory, the sub-directory will be considered the root of the project for that asconfig.json file. You can certainly update the paths in asconfig.json (like ../src instead of ./src and ../bin instead of ./bin). However, there may be some issues. For instance, if the workspace folder doesn't contain an asconfig.json at its root, VSCode won't know to activate the extension until you open an .as or an .mxml file in an editor. Even then, it may not initialize properly because the asconfig.json file isn't in one of the parent directories of the .as and .mxml files. |
Beta Was this translation helpful? Give feedback.
Similar to TypeScript's tsconfig.json, asconfig.json is intended to be placed at the root of the project, and not in a sub-directory.
vscode-as3mxml can detect asconfig.json files in sub-directories, and it treats each one as a separate project. However, when asconfig.json is in a sub-directory, the sub-directory will be considered the root of the project for that asconfig.json file. You can certainly update the paths in asconfig.json (like ../src instead of ./src and ../bin instead of ./bin). However, there may be some issues. For instance, if the workspace folder doesn't contain an asconfig.json at its root, VSCode won't know to activate the extension until you open an .as or an .mxml f…