-
Notifications
You must be signed in to change notification settings - Fork 43
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
Update to Groovy 3 #32
Comments
I've bumped the same today trying to verify that some strange compiler behavior occurs also on some other machine. |
It's not easy to update to Groovy 3 or provide a Groovy 3 flavor, as some dependencies needed by the project won't work with Groovy 3. |
That's great, thanks. :-) The background is this: https://issues.apache.org/jira/projects/GROOVY/issues/GROOVY-9975 This would instantly enable documentation, blogs and basically any website to have interactive syntax-highlighted editable runnable Groovy examples. For example look at the first two examples on https://kotlinlang.org/docs/null-safety.html#nullable-types-and-non-null-types, there you can see that component in action. I was even able to make it work for the happy path with the current codebase in this repository by allowing CORS and adapting the call and response processing in the playground component. |
When working on the new console experiment, the idea of having the ability to make the Groovy documentation have runnable code snippets was indeed in my mind. We'll see if we get to implement it, but that would be nice :-) |
That would really be awesome. |
Is the code of the new web console already shared somewhere or is it just private play up to now? |
we would still have to fork that library and release our own version, I don't know how receptive JetBrains would be to extract the common functionality into a base component. |
it is in a private repo at the moment |
I've just made it public, in case others want to contribute too. The URL for the repository is here: |
Would be nice to have an updated version for Groovy 3. :-)
The text was updated successfully, but these errors were encountered: