kotter
github-workflows-kt
kotter | github-workflows-kt | |
---|---|---|
14 | 8 | |
526 | 482 | |
0.6% | 0.8% | |
8.2 | 9.7 | |
15 days ago | 6 days ago | |
Kotlin | Kotlin | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kotter
-
What are the real use cases that led you to use Kotlin extension functions or properties in your projects?
You can check out my project https://github.com/varabyte/kotter if you want to see something that makes heavy use of extension functions (even though if you're a beginner using it, you probably wouldn't notice, because Intellij IDEA is so good about auto-importing things for you).
-
Kotlin Multiplatform User Survey: Q2 2023
Actually, more often than not I was talking about this library: https://github.com/varabyte/kotter. With a smattering of https://github.com/varabyte/truthish.
-
Looking for Kotlin Console UI libraries that work in IDE Terminal
I'm currently using Picnic and Mordant which are working nicely. I've tried out Kotter and Text-IO, but they either open a Swing terminal or require you to run a `.bat` script or something.
- Guides for Kotlin scripting use case
-
Kotlin CLI apps development status
I'm not too sure how to answer your question about language features in Kotter. Except maybe to point you at its extensive README and large collection of examples.
-
Kotter (a Kotlin-idiomatic library for writing dynamic console application) hits 1.0!
The first few examples I wrote were fairly bland, basically shaping and testing features as I created them. text, anim, blink, and input are in that category. (Plus, Kotter didn't have unit tests in the early days; instead, I just ran those programs over and over and over again).
-
What is your Kotlin project?
https://github.com/varabyte/kotter - A library for writing dynamic console applications.
-
Demaking Wordle in the terminal using Kotlin
You can find the project for the code here. As it's just an example project and not some final production codebase, so there's only a single source file in it, main.kt. It clocks in at 462 lines of code to accomplish everything you see above, and it took about a day.
-
I've created a small library for interactive CLI UI called 'kotlin-inquirer'
Hey OP, maybe it's overkill for you to change the implementation at this point but I wrote https://github.com/varabyte/kotter which is a Kotlin terminal library that runs your app in a virtual terminal if it can't run otherwise (e.g. in the intellij terminal). You'd probably be able to use it as a backend for inquirer if you were interested.
-
Introducing Konsole: A Kotlin-idiomatic library for writing dynamic command line applications
Gotcha! I created https://github.com/varabyte/konsole/issues/63 based on this conversation. Feel free to review it and add anything I may not have captured.
github-workflows-kt
- GitHub Actions could be so much better
-
XML is better than YAML
We use Kotlin to generate the yaml for our github actions: https://github.com/typesafegithub/github-workflows-kt
Nothing like a good old type safe compiled language to cut down on the verbosity, copy paste usage, silly syntax errors, weird undocumented you just have to know the magical incantations, etc. Kotlin or similar languages are the way to go. Much safer, more compact, easier to cut down on the copy paste reuse (which is just miserable drudgery), easy to introduce some sane abstractions where that makes sense. You get auto completion. And if it compiles, it's likely to just work.
People keep on moving around the deck chairs on the proverbial Titanic when it comes to configuration languages. Substituting yaml for json or toml just moves the problems. And substituting those with XML just introduces other issues and only marginally improves things. Well formed xml is nice. But so is well formed json. Schemas help, if the urls don't 404 and you have tools that can actually do something with them. Which, as it turns out is mostly not a thing in practice. And without that, it's just repetitive bloat. XML with schemas becomes very hard to read quickly.
There's a reason, people started ignoring XML once json became popular: json does most of the essential stuff well enough that XML just isn't worth the effort. And if you have something where you'd actually need the complexity of XML, it's likely to be some really ugly bloated kind of thing where the last thing you'd want to do is edit it manually.
I've dealt with cloudformation in XML form at some point in my life. It sucks. Not just a little bit. It's an absolute piss poor format for a thing like that. Since such a thing was lacking at the time, we ended up actually building our own little tools to generate that xml. Hand editing it was just too painful. One mistake could corrupt your entire stack. And it takes ages to find out if you actually got it right. In Json form it's hardly any better. It's just one of those convoluted over-engineered things. Anyway, Json support for cloudformation was not there at the time and the difference is like asking whether you'd preferred to be shot or stabbed. It's going to suck either way.
-
Typesafe Github Workflows explained to a 5 years old
github-workflows-kt is a tool for creating GitHub Actions workflows in a type-safe script, helping you to build robust workflows for your GitHub projects without mistakes, with pleasure, in Kotlin.
-
Guides for Kotlin scripting use case
The github-workflows-kt project uses Kotlin scripting, and it recommends doing everything using main.kts, because it's easier.
-
Feature Flags in a CI Pipeline
I use matrix tests with github actions to test my kt-search client with different versions of elastisearch and opensearch. Pretty easy to set up: https://github.com/jillesvangurp/kt-search/blob/master/.gith...
Basically it fires up elasticsearch using docker-compose and then the integration tests run against that. You could use a similar strategy to test different feature flag combinations.
For some of our private projects, we use kts to generate the github action yaml files using this: https://github.com/krzema12/github-workflows-kt
Well worth checking out if you have more complex workflows. Yaml is just horrible in terms of copy paste reuse. Also nice to get some compile time safety and auto complete with our action files.
-
Kts Scripting of Yaml & Json Dialects
One of my team members, Nikky, got annoyed with the verbosity and insane amount of copy-paste reuse needed to drive Github Actions. And true to her nature, promptly fixed it by using and contributing to GitHub Actions Kotlin DSL
-
GitHub Actions: a New Hope in YAML Wasteland
GitHub: https://github.com/krzema12/github-actions-kotlin-dsl
- GitHub Actions Kotlin DSL
What are some alternatives?
kotlin-inquirer - A collection of common interactive command line user interfaces written in Kotlin
kohttp - Kotlin DSL http client
JLine - JLine is a Java library for handling console input.
setup-wsl - A GitHub action to install and setup a Linux distribution for the Windows Subsystem for Linux (WSL)
kiwix-android - Kiwix for Android
maven-simple - Example Maven project demonstrating the use of
mosaic - An experimental tool for building console UI in Kotlin using the Jetpack Compose compiler/runtime
nix-configs - My Nix{OS} configuration files
clikt - Multiplatform command line interface parsing for Kotlin
kotlinpoet - A Kotlin API for generating .kt source files.
karel - Karel The Robot
github-actions-typing - Bring type-safety to your GitHub actions' API!