Skip to content

Issues: dolittle-obsolete/vscode

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

17 Open 9 Closed
17 Open 9 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Use new tooling platform
#28 opened Jun 27, 2019 by woksin
@woksin
Convert to TS
#27 opened May 22, 2019 by woksin
@woksin
Rename support for artifacts - preferably hooked into existing rename refactoring
#25 opened Mar 4, 2019 by einari
When creating an artifact (Command, ReadModel, Concept...) - it should automatically open the file that it created
#24 opened Feb 13, 2019 by einari
"Failed to load dolittle projects" when opening a non Dolittle Bounded Context / Application project bug Something isn't working
#23 opened Feb 12, 2019 by einari
dolittle run tooling
#22 opened Feb 4, 2019 by woksin
@woksin
Adding things using F1 -> Add <artifact> does not work - doesn't do anything bug Something isn't working
#21 opened Jan 28, 2019 by einari
When opening a sub folder containing a Bounded Context it can't find the application.json file and won't start the extension properly bug Something isn't working
#20 opened Jan 17, 2019 by einari
It would be nice if Dolittle Build (not current) built the entire solution and not context aware like it does now enhancement New feature or request tooling
#19 opened Jan 17, 2019 by einari
@woksin
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 enhancement New feature or request tooling
#18 opened Jan 17, 2019 by einari
@woksin
Dolittle project output has extra newlines for tools run in it - plus unwanted characters bug Something isn't working tooling
#17 opened Jan 17, 2019 by einari
Dolittle Project output should respect the colors typically coming for warnings / errors enhancement New feature or request tooling
#16 opened Jan 17, 2019 by einari
@woksin
Errors should not be displayed when opening non-Dolittle project folders tooling
#15 opened Jan 16, 2019 by jakhog
@woksin
Create icons vscode enhancement New feature or request ready
#12 opened Jan 5, 2019 by woksin
15 tasks
@Virrum
5
Debug for .NET projects without relying on launch.json
#11 opened Dec 14, 2018 by einari
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 epic in progress
#10 opened Dec 3, 2018 by einari
@woksin
Publish package for current project locally hold ready
#4 opened Feb 17, 2018 by einari
@woksin
1
ProTip! Follow long discussions with comments:>50.