The version of the org.eclipse.jdt.core.compiler.source=1.5 in the org.eclipse.jdt.core.prefs file is set to a very old version. Please change it to version 17, so that we don’t get “errors” in code completion for newer features.
What problem(s) would this feature solve?
Better code completion without red lines for code that actually works.
Explain what you were trying to do when you came across the problem leading to this feature request
I was writing code with lambda expressions in Java, where the code intelligence says that this is only available on source 1.8 or above, despite the compiler and runtime being at version 17.
I tried to change the version myself in the above mentioned file, but after a short while or a repl restart, it automatically changes the version back to 1.5. Please either allow us to change/customise it, or change it on your end.
just to be clear, replit staff all have a flair with the replit logo on their profile picture. Not that we like pinging of staff either.
And this “bug” is a trait of JDT which happens to be used by replit but is designed to be friendly for Eclipse users (just search on Google). To have replit change the default version on the Java template would make this a Feedback/General Problems topic.
Well, this solution has stopped working unfortunately. And now all my directories are not recognised as project files by Maven no matter what I do. Seems to be the right time to just give up on Replit. It shows a lot of potential, but there’s just too much stuff not working properly for it to actually be viable as anything but a tool to learn basic stuff.