Do a preliminary check for rascal project setup when starting a REPL

[DavyLandman]

This fixes #330.

You would get a message like this if you start a REPL without having a RASCAL.MF file in the correct location:

[DavyLandman]

We can also make these errors non-modal:

but not sure if that might be too subtle.

(you can expand it for more details: )

[jurgenvinju]

BTW, the "Takeout" project also has the problem of a capital T in its name. Do we check for this too?

[DavyLandman]

BTW, the "Takeout" project also has the problem of a capital T in its name. Do we check for this too?

our rascal.mf validator does. but that was missing at the moment :)

[DavyLandman]

It's a trade-off, should we try and make a full (in rascal) checker and fixer of project setups, or just detect most frequent errors, and point to the right way to construct a project?

I'm all in favor of making a nicer experience for our users, but we don't have to do that all at once.

[jurgenvinju]

It's a trade-off, should we try and make a full (in rascal) checker and fixer of project setups, or just detect most frequent errors, and point to the right way to construct a project?

Definitely we should not try and make a full rascal project fixer and checker. There is no bandwidth for that. We should keep doing what you've been doing: making essential improvements.

[DavyLandman]

@jurgenvinju agreed.

I've added a button so you can open the relevant documentation on our site, just to help users on the way to do it. and we can think about a proper way to fix the project setups later on.

could you review the messages?

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information