Repository navigation
✨ Tasks (Run scripts in the shell) #262
Description
Activity
@jasonplatts, I think that it's related to #76
Reacted by Jason Platts@pkasila : I don't know, do you think such a thing could be useful?
Do you see it more as a plugin?My take on this is that we should enable it in our plugin API so plugin developers can choose what action they want to perform on "play". Similar to how VSCode handles it.
Reacted by Pavel Kasila and Jason PlattsAs @lukepistrol said, we implement API for extensions to provide targets, tests and so on. So, NodeJS extension reads
package.jsonand createsnpm starttarget and anything else using Extension API and these targets appear in the UIYeah, I agree. It seems like it might be better as an extension. Nova offers tasks, https://docs.nova.app/extensions/run-configurations/.
- addedextensionsIssues related to the extension architecture in CodeEditIssues related to the extension architecture in CodeEdit
on Mar 27, 2022 - changed the title
[-][FEAT] - Run scripts in the shell[/-][+][FEAT] Tasks (Run scripts in the shell)[/+]on Mar 27, 2022 As @lukepistrol said, we implement API for extensions to provide targets, tests and so on. So, NodeJS extension reads
package.jsonand createsnpm starttarget and anything else using Extension API and these targets appear in the UIHere is the link to VS Code tasks. https://code.visualstudio.com/docs/editor/tasks
- changed the title
[-][FEAT] Tasks (Run scripts in the shell)[/-][+]✨ Tasks (Run scripts in the shell)[/+]on Mar 31, 2022 Overview
The Task Provider should allow extension developers to define external tools that can be run from a CodeEdit menu option and the command palette. These tasks should be capable of running command line tools, such as Grunt, npm, Rake, Gulp, etc. Results from running these tasks should appear in the console within CodeEdit.
Resources
https://code.visualstudio.com/docs/editor/tasks
https://code.visualstudio.com/api/extension-guides/task-providerReacted by Austin Condiff and Lingxi Li6 remaining items
I'm taking my hand at this and on discord there is general agreement that there should be some kind of configuration that users can access on how the project is run, how should this be implemented?
@iggy890 I don’t want to step on your toes with this but based on your latest commits in PRs I think this is better suited for a more experienced developer since this will be an important part of the app and most possibly it needs to align with our yet-to-come extensions API.
Reacted by Austin Condiff and iggy890@iggy890 I don’t want to step on your toes with this but based on your latest commits in PRs I think this is better suited for a more experienced developer since this will be an important part of the app and most possibly it needs to align with our yet-to-come extensions API.
That makes sense my basic implementation is here (someone could continue it here just create a PR or DM me on discord and I'll add you as a contributor to that branch): https://github.com/iggy890/CodeEdit/tree/run-code
@lukepistrol : I'd give @iggy890 a chance, creating an initial base wouldn't be bad.
Small suggestion adding to my prev comment: #262 (comment):
like IntelliJ, the standard option is just to run the current file.
but if you want to have some custom configuration, you can create a new configuration file for that workspace with the dropdown. but it defaults to just running the current fileCodeedit would need to have some custom task.json file that would read the custom config.
Don't know how npm scripts would work, identifynpm startas standard?- added a commit that references this issue
on Jul 28, 2024 Yes, this app will need such a thing to run different files instead of just keep modifying the paths!
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fields🏁 Complete


Is your feature request related to a problem? Please describe.
Registrazione.schermo.2022-03-26.alle.09.30.34.mov
You know that XCode has a menu like this, which allows you to run tests and other things as well as run the program.
It would be useful to have something like this, but which allows you to run scripts found in the
package.jsonfile.Script package.json example:
Describe the solution you'd like
So if the project contains a
package.jsonfile it tries to read it, if it finds any scripts, it puts them in the menu to let you run them.When one of the scripts is pressed, it starts the script in a new shell.