Kotlin scripting#61
Open
Cybermaxke wants to merge 1 commit into
Open
Conversation
|
Just thought of this: https://kotlinlang.org/docs/reference/whatsnew13.html#scripting-update Btw, I really like the idea of having such "config scripts". |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some thoughts on how we could use kotlin scripting in lantern to replace the current JSON + groovy scripting config files.
Vanilla JSON data packs will still be supported, everything else will be replaced by this kind of scripts. It's more powerful and it reduces the amount of work we have to put into parsing the config files. There will always a learning curve to write configs/scripts, then it's probably better to invest the time in a easy to use (but powerful) scripting API.
It also allows you to use a IDE (intellij) to write these scripts, providing a easy to use environment to write these scripts isn't in the scope of this PR. This will be a separate project/PR in the future. This is purely for scripting capabilities.
Currently built on top of the behaviors branch because there were changes I needed.