dolittle-obsolete vscode issues

dolittle-obsolete / vscode

Visual Studio Code extension

MIT License

0 stars 1 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Use new tooling platform

#28 woksin opened 5 years ago
0
Convert to TS

#27 woksin opened 5 years ago
0
Snippet support

#26 pavsaund closed 5 years ago
1
Rename support for artifacts - preferably hooked into existing rename refactoring

#25 einari opened 5 years ago
0
When creating an artifact (Command, ReadModel, Concept...) - it should automatically open the file that it created

#24 einari opened 5 years ago
0
"Failed to load dolittle projects" when opening a non Dolittle Bounded Context / Application project

#23 einari opened 5 years ago
0
dolittle run

#22 woksin opened 5 years ago
0
Adding things using F1 -> Add <artifact> does not work - doesn't do anything

#21 einari opened 5 years ago
0
When opening a sub folder containing a Bounded Context it can't find the application.json file and won't start the extension properly

#20 einari opened 5 years ago
0
It would be nice if Dolittle Build (not current) built the entire solution and not context aware like it does now

#19 einari opened 5 years ago
0
When using Dolittle Build / Build Current it would be nice to have the option of it popping up the dolittle project output window if an error occurred

#18 einari opened 5 years ago
0
Dolittle project output has extra newlines for tools run in it - plus unwanted characters

#17 einari opened 5 years ago
0
Dolittle Project output should respect the colors typically coming for warnings / errors

#16 einari opened 5 years ago
0
Errors should not be displayed when opening non-Dolittle project folders

#15 jakhog opened 5 years ago
0
logo should look more fit in the activitybar

#14 Virrum closed 5 years ago
0
The TreeView icon is a little larger than other icons

#13 pavsaund closed 5 years ago
2
Create icons vscode

#12 woksin opened 5 years ago
5
Debug for .NET projects without relying on launch.json

#11 einari opened 5 years ago
1
As a Dolittle dev, we want to be able to get rid of the .vscode symbolic link we have from the DotNET.Build submodule

#10 einari opened 5 years ago
0
Create new bounded context

#9 einari closed 5 years ago
0
Create new application

#8 einari closed 5 years ago
0
Add file types support

#7 einari closed 5 years ago
0
Rerun tests without building

#6 einari closed 5 years ago
0
Dotnet restore for current project based on focused file

#5 einari closed 5 years ago
0
Publish package for current project locally

#4 einari opened 6 years ago
1
Run tests for current project

#3 einari closed 5 years ago
0
Support building current and its dependencies

#2 einari closed 5 years ago
0
Support for building current project based on highlighted file

#1 einari closed 5 years ago
0