https://ruslan.ibragimov.by/categories/highlights/ Recent content in Highlights on Zero Entropy Hugo en Sun, 11 Aug 2024 00:00:00 +0000 https://ruslan.ibragimov.by/2024/08/11/koin-puzzler/ Sun, 11 Aug 2024 00:00:00 +0000 https://ruslan.ibragimov.by/2024/08/11/koin-puzzler/ I started using Koin starting from version 2.0.1, almost five years ago. Back then, I hadn’t yet seen how it was possible to write even large Kotlin applications that would be easy to test without using something from the set: spring-context, guice, koin, kodein, etc. At that time, to get an “isolated” Koin context instead of the default global one, you had to use the following approach: suspend fun main() { val agentModule = module { single<AgentApplication>() // . https://ruslan.ibragimov.by/2021/02/04/publish-maven-artifact-to-s3/ Thu, 04 Feb 2021 00:00:00 +0000 https://ruslan.ibragimov.by/2021/02/04/publish-maven-artifact-to-s3/ Create AWS account https://aws.amazon.com/ Create AWS S3 Bucket and make it public Bucket policy { "Version": "2012-10-17", "Statement": [ { "Sid": "PublicRead", "Effect": "Allow", "Principal": "*", "Action": [ "s3:GetObject", "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::bucket-name", "arn:aws:s3:::bucket-name/*" ] } ] } Create AWS Credentials Create IAM Policy Create IAM Group Create IAM User AWS Credentials AWS_ACCESS_KEY_ID: AKIAWEMDLXBHKYY2SV45 AWS_SECRET_ACCESS_KEY: kUr2HUHcDlDkqBkIZw6//HXzk3j7Wmzs3fFBB+JV Setup maven-publish plugin in Gradle plugins { kotlin("jvm").version("1.4.21") `maven-publish` } group = "io.heapy.deploy-sample" version = "1. https://ruslan.ibragimov.by/2019/08/26/slf4j-fluent-api-kotlin/ Mon, 26 Aug 2019 00:00:00 +0000 https://ruslan.ibragimov.by/2019/08/26/slf4j-fluent-api-kotlin/ SLF4J 2.0.0 introduced new logging API: logger.atInfo().log("Hello world") New fluent api looks more verbose in simple cases like this. Let’s compare it to traditional API: // traditional logger.info("Hello world") // fluent logger.atInfo().log("Hello world") You may think that more advanced use-cases will be more readable or shorter. Let’s check: logger.debug("Temperature set to {}. Old temperature was {}.", newT, oldT) logger.atDebug().addArgument(newT).addArgument(oldT).log("Temperature set to {}. Old temperature was {}.") logger.atDebug().log("Temperature set to {}. Old temperature was {}. https://ruslan.ibragimov.by/2019/08/25/benefits-of-kotlin/ Sun, 25 Aug 2019 00:00:00 +0000 https://ruslan.ibragimov.by/2019/08/25/benefits-of-kotlin/ This post was triggered by following tweet: Again and again I see as people compare languages/frameworks/approaches using only qualities which makes X looking better than Y, completely ignoring benefits that Y gives. There are was some java code in OkHttp library, and it’s backward-compatible replacement written in Kotlin. Cool thing is, that even when Kotlin code backward compatible, it do much more than Java and already more readable and concise! https://ruslan.ibragimov.by/2019/03/29/how-to-write-typed-middleware-in-redux/ Fri, 29 Mar 2019 00:00:00 +0000 https://ruslan.ibragimov.by/2019/03/29/how-to-write-typed-middleware-in-redux/ Just a small snippet which uses TypeScript to define types in middleware declaration. So implementation of middleware becomes possible even without documentation: you just use types to understand what functions do! import {Action, Dispatch, Middleware, Store} from "redux"; import {AppState} from "./store/AppState"; export function createMiddleware(): Middleware { return function (store: Store<AppState>) { return function (next: Dispatch) { return function (action: Action): Action { return next(action) } } } } Where AppState is simple interface which represents object stored in redux store. https://ruslan.ibragimov.by/2018/11/15/gradle-5.0-java-heap-space/ Thu, 15 Nov 2018 00:00:00 +0000 https://ruslan.ibragimov.by/2018/11/15/gradle-5.0-java-heap-space/ Today I try to update my work project to latest and greatest gradle 5.0-rc-2, and all works fine on my machine, but on CI I get the following error: $ export GRADLE_USER_HOME="$(pwd)/.gradle" $ ./gradlew check installDist Downloading https://services.gradle.org/distributions/gradle-5.0-rc-2-all.zip ........................................................................................................................... Welcome to Gradle 5.0-rc-2! Here are the highlights of this release: - Kotlin DSL 1.0 - Task timeouts - Dependency alignment aka BOM support - Interactive `gradle init` For more details see https://docs. https://ruslan.ibragimov.by/2018/11/14/how-to-use-kotlin-dev-repository-with-gradle-kotlin-dsl/ Wed, 14 Nov 2018 00:00:00 +0000 https://ruslan.ibragimov.by/2018/11/14/how-to-use-kotlin-dev-repository-with-gradle-kotlin-dsl/ If you try to use some dev version of kotlin, for example: // file: build.gradle.kts plugins { kotlin("jvm").version("1.3.20-dev-1612") } You will get the following exception: * What went wrong: Plugin [id: 'org.jetbrains.kotlin.jvm', version: '1.3.20-dev-1612'] was not found in any of the following sources: - Gradle Core Plugins (plugin is not in 'org.gradle' namespace) - Plugin Repositories (could not resolve plugin artifact 'org.jetbrains.kotlin.jvm:org.jetbrains.kotlin.jvm.gradle.plugin:1.3.20-dev-1612') Searched in the following repositories: BintrayJCenter Gradle Central Plugin Repository In old-fashion buildscript block you can define repositories, but with shiny new plugins block it’s impossible. https://ruslan.ibragimov.by/2017/06/08/how-to-use-apache-asynchttpclient-with-kotlin-coroutines/ Thu, 08 Jun 2017 00:00:00 +0000 https://ruslan.ibragimov.by/2017/06/08/how-to-use-apache-asynchttpclient-with-kotlin-coroutines/ upd. Code updated to work with Kotlin 1.3 and stable coroutines. If you try to use Apache Async HttpClient with Kotlin coroutines you will found that their API (execute method) returns java.util.concurrent.Future that can’t be simply used with coroutines. But, you also allowed to pass future callback to execute method: // interface HttpAsyncClient Future<HttpResponse> execute( HttpUriRequest request, FutureCallback<HttpResponse> callback ); Let’s take a look at FutureCallback interface: public interface FutureCallback<T> { void completed(T result); void failed(Exception ex); void cancelled(); } Step 1: Init. https://ruslan.ibragimov.by/2017/05/23/small-scopes-and-srp-rocks-isnt-it/ Tue, 23 May 2017 00:00:00 +0000 https://ruslan.ibragimov.by/2017/05/23/small-scopes-and-srp-rocks-isnt-it/ We discussing recent post by “OOP” funboy Yegor Bugayenko. My thoughts that it’s not about FP or OOP, objects or functions, it’s all about SRP. Like we have two initialization blocks in one method, and then we test results of these blocks. We can move this blocks in lambdas/functions/classes, but in general it’s just two functions that produces a and b and then we compare a and b. After working with Kotlin I’ll write this test like: https://ruslan.ibragimov.by/2016/02/06/awesome-kotlin/ Sat, 06 Feb 2016 00:00:00 +0000 https://ruslan.ibragimov.by/2016/02/06/awesome-kotlin/ Yay, Kotlin at the finish line to release, and for help you finding valuable project Awesome Kotlin list exists! Feel free to spread it over the Internet and contribute new links and projects. Happy coding with Kotlin!