Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

User defined Che tasks commands should be exported in a tasks.json file

See original GitHub issue

Description

Currently, when a user defines a command (in a devfile or from the Che dashboard), he won’t be able to view/edit it from the tasks.json where Theia custom tasks should be defined.

Issue Analytics

State:
Created 5 years ago
Comments:15 (15 by maintainers)

Top GitHub Comments

1reaction

l0rdcommented, Apr 8, 2019

I suggest to discuss that tomorrow in Cherkasy during our meeting about Che commands. We will then report the outcome of the discussion here.

1reaction

RomanNikitenkocommented, Apr 3, 2019

As it was suggested within this issue I added ability to configure Task from UI:

‘Configure task’ action was provided for each item of ‘Run Task’ menu
‘Configure Tasks’ menu action was added

‘Configure Tasks’ menu displays only detected tasks. ‘Run Task’ menu displays both: configured and filtered detected tasks. Detected tasks are filtered by label: for example, when we have configured and detected tasks with the same label - only configured task is displayed. Both menus allow to copy task configuration to tasks.json file and provide ability to edit this one.

So, Che Commands from WS config are ‘detected task’ for Theia API and are displayed as items of ‘Configure Tasks’ and ‘Run Task’ menus. Task configuration is copied to tasks.json and available for editing by clicking on appropriate item. After that che command is displayed as ‘configured’ in ‘Run Task’ menu and has high priority at running. At the same time task configuration from WS config is still available from ‘Configure Tasks’ menu.

I would like to discuss question - do we need to copy all Che Commands from WS config to tasks.json file without user interaction?

Top Results From Across the Web

Tasks in Visual Studio Code

Integrate with External Tools via Tasks. Lots of tools exist to automate tasks like linting, building, packaging, testing, or deploying software systems.

Chapter 3. Developer workspaces - Red Hat Customer Portal

Elements of the project, such as the path, git location, or branch. · Commands to perform daily tasks such as build, run, test,...

Server Administration Guide - Keycloak

A user role mapping defines a mapping between a role and a user. A user can be associated with zero or more roles....

VScode: Defining own variables in tasks.json - Stack Overflow

After executing the "Process Task.json" task, all variables in $[] format will be replaced by its corresponding value. Share.

How to export all issues from Jira via API - Atlassian Community

With the below API, you can simply perform this task, not only does it save you time, you can have all your project...