How can I find tasks.json since it's no longer under /projects folder?
See original GitHub issueSummary
I have updated the devfile to use latest version from theia, today I am creating a new workspace, and the directory .theia in the project folder is no longer used and not created, I created it and yet it’s still not used.
Because I am using promptString and shell tasks, I don’t know how to write these in the devfile, so what I do, is that I created a tasks that overwrites the tasks.json. Can you please advise a workaround or share examples of devfiles with shell tasks and input are used?
Relevant information
Version: Che-Theia@9d3a00a using Theia@c837b6cb
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (12 by maintainers)
Top Results From Across the Web
Where is the tasks.json file in vscode? - Stack Overflow
Open a folder with vscode; Hit F1; Select "Tasks: Configure Task"; Hit Enter and vscode will create a sample tasks.json for you.
Read more >Tasks in Visual Studio Code
You can create user level tasks that are not tied to a specific workspace or folder using the Tasks: Open User Tasks command....
Read more >Customize build debug tasks with JSON files - Visual Studio ...
You can configure a new task by right-clicking on a file or folder and selecting Configure Tasks. This creates (or opens) the tasks....
Read more >Scripting with VSCode Tasks and Typescript
I'm not under the delusion that I can prevent all errors before I run ... I'm going to create a new project folder...
Read more >Angular workspace configuration
The angular.json file at the root level of an Angular workspace provides ... The projects section of the configuration file does not correspond...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In the end, the mystery is not that deep:
should read
@SDAdham does that fix your problem? I agree writing a message to a log the user never sees is not the best way to help the user 🤷
Issues go stale after
180
days of inactivity.lifecycle/stale
issues rot after an additional7
days of inactivity and eventually close.Mark the issue as fresh with
/remove-lifecycle stale
in a new comment.If this issue is safe to close now please do so.
Moderators: Add
lifecycle/frozen
label to avoid stale mode.