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.

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

Jump to bottom

Uniformize developer experience using Visual Studio Code Dev Containers #1059

Open
tschaffter opened this issue Dec 16, 2022 · 1 comment · May be fixed by #1060
Open

Uniformize developer experience using Visual Studio Code Dev Containers #1059

tschaffter opened this issue Dec 16, 2022 · 1 comment · May be fixed by #1060
Labels
feature

Comments

@tschaffter
Copy link
Member

Is your feature request related to a problem? Please describe.

  • Problem 1: The developers use different development environment with different tool versions. For example, the README asks developers to install poetry manually but does not specify which version to install. Different development environment may lead to different tool output.
  • Problem 2: The developer need to install tools manually (e.g. poetry). This step can automated.

Describe the solution you'd like

Uniformize developer tooling using a dev container (see dev container standard).

How important is this feature? Select from the options below:
• 🌗 Medium - can do work without it; but it's important (e.g. to save time or for convenience)

When will use cases depending on this become relevant? Select from the options below:
• Using a dev container would make it easier for developer to potentially use the computation caching feature of Nx for the sake of saving time on tasks such as lint, build and test (tracked in separate ticket).
@tschaffter
Copy link
Member Author

@milen-sage You could assign this ticket to me. I already started working on a feature branch to add a dev container definition to this project. I will accompany the PR with a video that explains how developers would use this dev container to standarding your team's tools.

@tschaffter tschaffter linked a pull request Dec 16, 2022 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Add dev container tschaffter/schematic
1 participant
@tschaffter