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

feat: Integrated Debugging Configuration for VSCode with Jaspr #202

Open
carmas123 opened this issue Apr 4, 2024 · 1 comment
Open

feat: Integrated Debugging Configuration for VSCode with Jaspr #202

carmas123 opened this issue Apr 4, 2024 · 1 comment
Labels

Comments

@carmas123
Copy link
Contributor

carmas123 commented Apr 4, 2024

Description:
To enhance the development efficiency and effectiveness with the Jaspr framework, I propose the introduction of an integrated debugging configuration specifically for Visual Studio Code (VSCode). The aim is to provide developers with a ready-to-use solution that allows for seamless debugging of Jaspr code directly within the IDE, eliminating the need for complex manual configuration.

Use Case:
Currently, debugging applications developed with Jaspr in VSCode requires developers to undergo a manual configuration process that can be both time-consuming and error-prone. This process involves creating project-specific configuration files and adjusting IDE settings. An integrated debugging configuration would significantly simplify this process, making debugging more accessible to developers of all experience levels.

Suggested Implementation:
It is suggested that the Jaspr framework include a set of predefined configuration files for debugging in VSCode, along with a detailed guide on how to utilize them. These files should be easily importable into any Jaspr project and customizable to fit different development needs. Additionally, it would be beneficial if this configuration could be automatically recognized and applied by VSCode upon opening a Jaspr project.

Example Configuration:
A potential predefined configuration could include:

  • A .vscode/launch.json file set up to start the Jaspr development server and attach the VSCode debugger.
  • A set of tasks in .vscode/tasks.json to execute common Jaspr commands, like building the project or starting in debug mode.
  • Code snippets and hints for fixing common errors encountered during debugging.

Benefits:

  • Improved Productivity: Developers can start debugging immediately, reducing the time needed for environment setup.
  • Accessibility: Makes the debugging process less intimidating for newcomers and more efficient for experienced users.
  • Code Quality: By facilitating debugging, developers can more quickly identify and resolve issues and bugs, improving the overall quality of the code.

Conclusion:
Integrating a specific debugging configuration for VSCode would significantly improve the development experience with Jaspr, making it an even more attractive framework for the developer community. Simplified and integrated access to debugging features would not only increase efficiency but also developer satisfaction when working on Jaspr projects.

@schultek
Copy link
Owner

schultek commented Apr 5, 2024

Fully agree about the benefits to DX.

I'm not sure if this would better be part of the jaspr tooling, or an actual vscode extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants