Skip to content
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.

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

Remove references to VSCode from development flow #6079

Closed
gorkem opened this issue Aug 31, 2019 · 2 comments
Closed

Remove references to VSCode from development flow #6079

gorkem opened this issue Aug 31, 2019 · 2 comments
Assignees
Labels
contributor experience issues related to the contributor experience documentation issues related to documentation

Comments

@gorkem
Copy link
Contributor

gorkem commented Aug 31, 2019

We should not reference VSCode for developing Theia. Instead our development flow should reference the either of the example builds. Right now it looks like debugging Theia is only done with VSCode.

@akosyakov
Copy link
Member

Do you mean only in docs? We cannot remove vscode settings files, since there are no Theia based desktop distributions yet for dogfooding. If there would be I am for completely switching to Theia settings and force contributors to use electron version instead on desktop. Hope we get there later this year.

For now, I can rephrase that one can develop with any Theia IDE or VS Code.

@akosyakov akosyakov added contributor experience issues related to the contributor experience documentation issues related to documentation proposal feature proposals (potential future features) labels Sep 1, 2019
@gorkem
Copy link
Contributor Author

gorkem commented Sep 2, 2019

I meant on docs, especially the development flow document. It is OK for now if we have the settings files for both IDEs on the repos.

@akosyakov akosyakov removed the proposal feature proposals (potential future features) label Sep 3, 2019
@akosyakov akosyakov self-assigned this Sep 3, 2019
akosyakov added a commit that referenced this issue Sep 3, 2019
akosyakov added a commit that referenced this issue Sep 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contributor experience issues related to the contributor experience documentation issues related to documentation
Projects
None yet
Development

No branches or pull requests

2 participants