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

Quick-fix for missing pom.xml #443

Open
jurgenvinju opened this issue Sep 2, 2024 · 0 comments
Open

Quick-fix for missing pom.xml #443

jurgenvinju opened this issue Sep 2, 2024 · 0 comments

Comments

@jurgenvinju
Copy link
Member

jurgenvinju commented Sep 2, 2024

The errors now shown at the "module" keyword would get a "code action" associated that generates the right pom.xml at the right place.

Propose to implement this in steps:

  • PR for code actions for Rascal files (first only associated with diagnostics)
  • PR for specific code action for missing pom.xml
  • PR for other code actions related to project setup.

Let's try to keep code analysis, generation and transformation actions as much as possible written in Rascal. Eat-your-own-dogfood is good for quality/testing but also communicates to users the potential of Rascal. For example, we could keep the current analysis in TS, but have the Commands executed by Rascal (exactly as in the DSL-parameterized LSP server).

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

No branches or pull requests

1 participant