Naresha

Groovy Scripts - Exploring Binding

In a previous post exploring scripting basics, we saw how binding was used to supply command-line arguments to scripts. In this post, let's explore the design of binding further. class BindingDemo { static void main(String[] args) { Binding sampleBinding = new Binding() println sampleBinding.variables sampleBinding.message = "Hello"

Don't fall in love with your code

I was mentoring this developer, and he was working on a piece of UI which involved a lot of JavaScript. The timeframe was before sing-page apps became the norm. So the team was using JQuery. Day by day, the functionality started getting more sophisticated. A part of the feature was

Effective Java with Groovy - Favour Internal Iterators

Let's start with the following code making use of the traditional for loop. List<String> languages = List.of("Java", "Groovy", "Kotlin"); // List.of() requires Java 9 or above for (int i = 0; i < languages.size(); i++) { System.out.println(

Gradle - running tests in Continuous Build

In a previous post, we saw Gradle's continuous build in action. If you use Test Driven Development at work, you will be running your tests after every code change. Let's leverage Gradle's continuous build so that you don't have to trigger the

Micronaut - Reloading using Gradle's Continuous Build

I have written about my thoughts on hot loading in general in this post. Micronaut from version 1.2 started supporting continuous build, but you had to manually add the configuration entries to your project. With the 2.0 version, Micronaut supports 'continuous build' out of the box.

Groovy Scripts - Functions and Variables

In a previous post, we explored the simplicity of scripting mode offered by Groovy. We arrived at the following code. String message = args.length > 0 ? "Hello ${args[0]}" : "Hello" println message Let's make the functionality slightly more sophisticated. Say, we want to send

Hot Loading - Still Relevant?

More than a decade ago, when I started my profession as a software developer, one of the most significant pain for developers was waiting for your application server to start so that they could verify their code changes. Hence there were efforts to make live reloading happen without restarting the

Effective Java with Groovy - Are you implementing equals and hashCode correctly?

Consider the following Groovy code. class Product { String sku String description BigDecimal price } Now let's put the Product class into use as follows. Product book1 = new Product(sku: 'P101', description: 'Effective Java', price: 599.0) Product book2 = new Product(sku: 'P101', description:

Gradle - Continuous Build

Back in 2015, Gradle introduced this feature which they called 'continuous build'. Those days, I was exploring Ratpack, and it was the first toolkit/ framework to leverage the continuous build feature. The idea here is to rerun the tasks whenever there is a code change. Gradle will first

Micronaut HTTP Client - just the response body

In a previous post, we used io.micronaut.http.client.BlockingHttpClient to get response from an HTTP endpoint. We used the exchange method as follows. HttpResponse response = client.toBlocking().exchange("/greeting", String) If you are using Java instead of Groovy, you will pass "String.class" instead