<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Fabio Miranda on Medium]]></title>
        <description><![CDATA[Stories by Fabio Miranda on Medium]]></description>
        <link>https://medium.com/@fabiomirgo?source=rss-c1dfeca69015------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XVcH1ugNmf70LS7nsrVf4Q.png</url>
            <title>Stories by Fabio Miranda on Medium</title>
            <link>https://medium.com/@fabiomirgo?source=rss-c1dfeca69015------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:24:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fabiomirgo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Kotlin's power: Build a DSL]]></title>
            <link>https://medium.com/@fabiomirgo/kotlins-power-build-a-dsl-1fcf215b7bb0?source=rss-c1dfeca69015------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fcf215b7bb0</guid>
            <category><![CDATA[jetbrains]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[dsl]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[kotlin-dsl]]></category>
            <dc:creator><![CDATA[Fabio Miranda]]></dc:creator>
            <pubDate>Tue, 09 Jun 2020 15:57:44 GMT</pubDate>
            <atom:updated>2020-06-10T05:11:27.551Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zg6oJ9DmH8PhxPnm.png" /><figcaption><a href="https://bugfender.com/blog/author/joseluis/">Jose Luis Franconetti</a>, via <a href="https://bugfender.com/blog/kotlin-for-android-development-heavyweight-language-or-hopeless-hype/">bugfender</a></figcaption></figure><p>Kotlin is a programming language created and maintained by JetBrains. Just for this only reason, we should have high expectations about it, after all, JetBrains is responsible for the creation of quality IDEs, with many resources, and that support several programming languages, which requires deep knowledge about them.</p><p>The JetBrains&#39; experience years, aligned with the motivation to create something to solve its problems, basically with Java, having as pillars, conciseness, and pragmatism, resulted in a powerful programming language, which is gaining more and more space, both in android development and back-end services.</p><p>One thing that makes this Kotlin’s power clearer, is the way we can build DSLs, as it requires the use of several resources of the language, which were thought of at the beginning of its creation: lambda with receivers, extension functions, infix functions, inline functions, reified types, smart cast, internal modifier, etc.</p><p>The idea of ​​this article is precise to show this: the power of the language, through the creation of a DSL, making use of some of its resources, and explaining the reason for using these resources.</p><p><strong>Attention:</strong> I will not go into detail to explain each Kotlin feature used here, each one of them, deserves an article for that. The idea of ​​this article, is to show some of these resources, and how we can use them to model an API, to the point of creating a DSL.</p><h3><strong>DSL — Domain-Specific</strong> Language</h3><p>Before starting to create a DSL, let’s define what a DSL is.</p><p>Domain-specific languages, or simply DSL, are characterized by dealing with just a single problem, ignoring what is not relevant to solve it, unlike languages with general purposes, such as, Kotlin, Java, or Python.</p><p>SQL and Regular Expressions are examples of DSLs, which you probably already know. The first is used to manipulate relational databases, and the second, for texts, they have specific domains, and there is no way to create entire applications only with them.</p><p>There are the external DSLs, which I just mentioned, and the internal DSLs, which are part of a project developed with a programming language with general purposes. The one we are going to create here is an internal DSL.</p><h3>Building a DSL in Kotlin</h3><p>The first thing that should be made clear is that there is no library or API in Kotlin, to create a DSL. What really exists are the features of the language itself, which allow you to model your APIs in the best possible way, so that it meets the rules of a specific DSL.</p><p>When I say APIs, I mean the communication interfaces in our set of classes, functions, and interactions, with the rest of the application. Just as a library provides an interface to be used, each class in an application provides an interface with possibilities for interaction.</p><p>A DSL in Kotlin is nothing more than an appropriated model of this interface, providing possibilities for interactions, which respect the rules of the DSL that you want to create.</p><p>The DSL we are going to create, is for SQL, and our goal is to write the following query, with our DSL:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/34da96e9276c2948eb9c771d3cfb98f0/href">https://medium.com/media/34da96e9276c2948eb9c771d3cfb98f0/href</a></iframe><p><strong>Constraints</strong></p><ul><li>Each table will refer to a <strong>data class</strong>;</li><li>Each column refers to a property of a <strong>data class</strong>;</li><li>The usage of the interface that we are going to create should be very close with the writing of the query above, allowing easy identification, that it is a DSL;</li></ul><p><strong>Final result</strong></p><p>As a final result, we will have the following Kotlin code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/033f7226d2b681623eb63f19409adffa/href">https://medium.com/media/033f7226d2b681623eb63f19409adffa/href</a></iframe><p>Note the similarity of the Kotlin code, with the SQL command.</p><p><strong>Step by step</strong></p><p><strong>1)</strong> Create a new <strong><em>Gradle Kotlin/JVM</em></strong> project, named <strong><em>sql-dsl</em></strong>. Use the Kotlin DSL for the build script, and configure <strong><em>build.gradle.kts</em></strong>:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0c12fd76955f3c15330120b0624706d2/href">https://medium.com/media/0c12fd76955f3c15330120b0624706d2/href</a></iframe><p>Let’s face the project as a library that will be used by other projects.</p><p><strong>2) </strong>Create the <strong><em>SelectCommand</em> </strong>and <strong><em>SelectBuilder</em> </strong>classes and the <strong><em>select()</em></strong> function below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f1f955ebfefe25ea5bd1b8ee7a6e06f0/href">https://medium.com/media/f1f955ebfefe25ea5bd1b8ee7a6e06f0/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2cb27071676d1d78e4fb8a1693aaf27a/href">https://medium.com/media/2cb27071676d1d78e4fb8a1693aaf27a/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/185bc9085b74ca7cc5ac064f0305c8bd/href">https://medium.com/media/185bc9085b74ca7cc5ac064f0305c8bd/href</a></iframe><ul><li><strong><em>SelectCommand</em></strong> is the class where the necessary properties and functions for the execution of a SELECT command will be;</li><li><strong><em>SelectBuilder</em></strong> is the class responsible for receiving the command, and generating the string for it;</li><li>The <strong><em>select()</em></strong> function, will be used by other classes, to interact with the library that we are creating, it basically creates a <strong><em>SelectBuilder</em></strong> and returns it;</li><li>The block parameter, of the <strong><em>select()</em></strong> function, is a <strong><em>lambda with receiver</em></strong>, and whoever calls the function, sees it as follows:</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8a8c080b49fbbc4baea879b91642d869/href">https://medium.com/media/8a8c080b49fbbc4baea879b91642d869/href</a></iframe><p>A lambda, which has a <strong><em>SelectCommand</em></strong> type receiver, allowing access to the properties of the <strong><em>SelectCommand</em></strong>, without necessarily having to create an instance of it.</p><p><strong>So far…</strong></p><ul><li>we created some classes, separating some responsibilities;</li><li>we started to worry about the interface of our library, when creating the <strong><em>select()</em></strong> function, with a <strong><em>lambda with receiver</em></strong>, because that way, the client that consumes our library, doesn&#39;t have the need to create the command, he just configures it, inside of a lambda, and later, this lambda is executed in the <strong><em>apply</em></strong> method.</li></ul><p><strong>3)</strong> Create the <strong><em>Table</em></strong> interface:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9b18922e22f12cb999ad9492b54eb1e1/href">https://medium.com/media/9b18922e22f12cb999ad9492b54eb1e1/href</a></iframe><p>Through this interface, we will identify the <strong>data class</strong> that refers to a table;</p><p><strong>4)</strong> Create the <strong>SelectCommandTest</strong> test class:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0714a5a07c661591eca66930aa524385/href">https://medium.com/media/0714a5a07c661591eca66930aa524385/href</a></iframe><p>As we proceed with the implementation, we will be changing the test’s <strong><em>generateSql()</em></strong> function, and following the evolution of the <strong><em>select()</em></strong> function, until it is possible to run the test and execute it successfully.</p><p><strong>5)</strong> Add the column option in the <strong><em>SelectCommand</em></strong> and <strong><em>SelectBuilder</em></strong> classes:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a06dafa0631fc62211e96823fce6ff9a/href">https://medium.com/media/a06dafa0631fc62211e96823fce6ff9a/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c8838347622c3cb5df546fd5891c3616/href">https://medium.com/media/c8838347622c3cb5df546fd5891c3616/href</a></iframe><ul><li>The columns of the SELECT command will be stored in a mutable list of type String;</li><li>The columns function expects to receive a <strong><em>vararg</em></strong> parameter of type <strong><em>KeyProperty&lt;T,R&gt;</em></strong>, where:</li></ul><p><strong>T:</strong> refers to the receiver of this property, and in the example, we are passing a new type parameter, which is a <strong><em>T</em></strong> <strong><em>subtype</em></strong> of <strong><em>Table</em></strong>;</p><p><strong>R:</strong> refers to the type of property, and in the example, we are going through, it&#39;s any type</p><p><em>In other words, we are saying: the </em><strong><em>columns()</em></strong><em> function, receives an array of properties of classes that must be a subtype of Table, and these properties themselves, can be of any type.</em></p><ul><li>The function is marked as <strong>inline</strong>, and the type parameter as <strong>reified</strong>, because we need to access <strong>type T</strong>, to get the name of the class to which the property refers at runtime because the name of the class will be the name of the table;</li></ul><p>It is now possible to add the columns in our test, change the <strong><em>generateSql()</em></strong> function, in the <strong><em>SelectCommandTest</em></strong> test class:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dae3d422aa9d8a9368b6b0507a2a8fbb/href">https://medium.com/media/dae3d422aa9d8a9368b6b0507a2a8fbb/href</a></iframe><p><strong>6)</strong> Improve the <strong><em>columns()</em></strong> function:</p><ul><li>Within <strong><em>Table</em></strong> file, create the <strong><em>extension function getColumnName()</em></strong></li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1d1e770168078ebc3166235cab0aafa1/href">https://medium.com/media/1d1e770168078ebc3166235cab0aafa1/href</a></iframe><ul><li>Change the <strong>columns()</strong> function:</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d7f206a711d1f84ae32231b436eb2237/href">https://medium.com/media/d7f206a711d1f84ae32231b436eb2237/href</a></iframe><p>So the responsibility of giving the column its own name remains with the property, and not the function, the function only asks the property for its name, which makes much more sense.</p><p><strong>7)</strong> Add the from clause in the <strong>SelectCommand()</strong> class, and consider the table in the <strong>SelectBuilder()</strong> class:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/40f7197ea3bbf384c0a99d0dcb10371e/href">https://medium.com/media/40f7197ea3bbf384c0a99d0dcb10371e/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5f90f004514f653ada04007ecc2362ba/href">https://medium.com/media/5f90f004514f653ada04007ecc2362ba/href</a></iframe><p>It is now possible to inform the table in the <strong><em>generateSql()</em></strong> function, in our <strong><em>SelectCommandTest</em></strong> test class:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a54f822b7a26f0fde33f89c246a4d09b/href">https://medium.com/media/a54f822b7a26f0fde33f89c246a4d09b/href</a></iframe><p><strong>8)</strong> Add the possibility to make JOINs between tables:</p><p><strong>8.1)</strong> Create <strong><em>JoinType</em></strong> enum:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cc4044f96a8efc276e5e232ff4d24a7c/href">https://medium.com/media/cc4044f96a8efc276e5e232ff4d24a7c/href</a></iframe><p><strong>8.2) </strong>Create<strong> <em>ConditionType</em></strong> enum:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1c6b867e4f523bd2814efeb597bb477a/href">https://medium.com/media/1c6b867e4f523bd2814efeb597bb477a/href</a></iframe><p><strong>8.3)</strong> Create the class <strong>Condition</strong>:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f3838302c00f0e2107ba65fd95255a9a/href">https://medium.com/media/f3838302c00f0e2107ba65fd95255a9a/href</a></iframe><p><strong>8.4) </strong>Create a class for the ON clause:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4beed3c377f5dc17f566f7857c26013d/href">https://medium.com/media/4beed3c377f5dc17f566f7857c26013d/href</a></iframe><p><strong>8.5)</strong> Create <strong><em>ConditionBuilders.kt</em></strong> file:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8d1386e8d869842d4cf0d8ad45051fdf/href">https://medium.com/media/8d1386e8d869842d4cf0d8ad45051fdf/href</a></iframe><ul><li>The <strong><em>eq()</em></strong> function is an extension function for all <strong><em>KProperty</em></strong> of <strong><em>T</em></strong>, where <strong><em>T</em></strong> is a <strong><em>subtype</em></strong> of a <strong><em>Table</em></strong>, that is, we are adding the function <strong><em>eq()</em></strong>, in every property of a table;</li><li>The <strong><em>eq()</em></strong> function is <strong><em>infix</em></strong>, that is, we don’t need the dot and parentheses to call it over an instance of a column;</li><li>The <strong><em>eq()</em></strong> function only returns an instance of a condition;</li></ul><p><strong>8.6) </strong>Create the <strong><em>TableWrapper</em></strong>:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cc73d158a6884070de724af8a3d9cdcb/href">https://medium.com/media/cc73d158a6884070de724af8a3d9cdcb/href</a></iframe><ul><li><strong>TableWrapper</strong> is a class that receives a table, and adds functionality to it;</li><li>In this case, the two functionalities are: <strong>innerJoin()</strong> and <strong>leftJoin()</strong>;</li><li>It also receives the <strong><em>joinType</em></strong> parameter with default null, because the table is not always involved in a join, as in the case of the table informed in the from clause;</li><li><strong><em>innerJoin()</em></strong> and <strong><em>leftJoin()</em></strong> are <strong><em>infix</em></strong> functions, which allows us to call them, over an instance of <strong><em>TableWrapper</em></strong>, without the dot and parentheses;</li><li>For each join function performed, a new instance of <strong><em>JoinWrapper</em></strong> is returned, which extends the <strong><em>TableWrapper</em></strong>, and adds the <strong><em>on()</em></strong> functionality;</li><li>In every join, the new instance of <strong><em>JoinWrapper</em></strong>, is saved in the next variable;</li><li><strong><em>on()</em></strong> is an <strong><em>infix</em></strong> function, which allows us to call it, over a <strong><em>JoinWrapper</em></strong> instance, without the dot and parentheses;</li><li><strong><em>on()</em></strong> takes only one parameter: a condition;</li><li>For each <strong>on()</strong> function performed, the <strong><em>JoinWrapper</em></strong> instance itself is returned, however, casting to <strong><em>TableWrapper</em></strong>, avoiding the client of our library from calling the <strong><em>on()</em></strong> function, over another <strong><em>on()</em></strong>;</li><li>The <strong><em>toString()</em></strong> function generates the SQL string, containing the table name, the JOINs, and the ON clauses;</li></ul><p><strong>8.7)</strong> Change the <strong><em>SelectCommand</em></strong>, and <strong><em>SelectBuilder</em></strong> classes, replacing the table with the <strong><em>tableWrapper</em></strong>:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4d2ee7ec4267a1c4fb7103a1ec3da3b5/href">https://medium.com/media/4d2ee7ec4267a1c4fb7103a1ec3da3b5/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/64ea9d2b0204df660b2355101b373034/href">https://medium.com/media/64ea9d2b0204df660b2355101b373034/href</a></iframe><p>It is now possible to inform the Joins in the <strong><em>generateSql()</em></strong> function, in our <strong><em>SelectCommandTest</em></strong> test class:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8bb8b4f94f2e081ec63a28e38506666a/href">https://medium.com/media/8bb8b4f94f2e081ec63a28e38506666a/href</a></iframe><p><strong>9)</strong> Add the where clause in <strong><em>SelectCommand</em></strong> and <strong><em>SelectBuilder</em></strong>:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5d1f1d8aeed50f2125abc4f4e3b9c600/href">https://medium.com/media/5d1f1d8aeed50f2125abc4f4e3b9c600/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/63273e7f1157d174e2d1d033e1243707/href">https://medium.com/media/63273e7f1157d174e2d1d033e1243707/href</a></iframe><p>It is now possible to inform the where clause in the <strong><em>generateSql()</em></strong> function, in our <strong><em>SelectCommandTest</em></strong> test class:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4a5086274691d1f90b7493aa20b1699c/href">https://medium.com/media/4a5086274691d1f90b7493aa20b1699c/href</a></iframe><p><strong>10)</strong> Add the functionality to transform any string into the snake case pattern, and change the query tables and columns to be returned in that pattern:</p><p><strong>10.1)</strong> Create <strong><em>StringFunctions.kt</em></strong> file, and add the extension function <strong><em>toSnakeCase()</em></strong> to the String class:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/65c81a503cf18f805867c991177811cf/href">https://medium.com/media/65c81a503cf18f805867c991177811cf/href</a></iframe><p><strong>10.2)</strong> Change the <strong>getColumnName() </strong>function:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f3dc69cc4f171479433c7c6fb955410f/href">https://medium.com/media/f3dc69cc4f171479433c7c6fb955410f/href</a></iframe><p><strong>10.3)</strong> Change the <strong><em>toString()</em> </strong>function<strong> </strong>in<strong> <em>TableWrapper</em> </strong>class:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ec5d5b0899aa7c91ce05366a14b19517/href">https://medium.com/media/ec5d5b0899aa7c91ce05366a14b19517/href</a></iframe><p>Now, it is possible to run the test successfully, we reached our goal of generating the query!</p><p>However, there is still work to be done. Our access modifiers need to be improved, remember that we are facing this project as a library, therefore we must be aware of things that can be used by a client external to our library, and allow access only to what they really should have. <strong>In other words, we should improve the interface of our library, making it public, only what really makes sense</strong>.</p><p><strong>11)</strong> Adjust the access modifiers:</p><p><strong>11.1)</strong> Change the <strong><em>columns()</em></strong> and <strong><em>from()</em></strong> functions in the <strong><em>SelectCommand</em></strong> class to be public and apply the <strong><em>@PublishedApi</em></strong> annotation to the <strong><em>columns</em></strong> and <strong><em>tableWrapper</em></strong> properties:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2b5a3e8dedb2e6c48dc7c79bb35be51f/href">https://medium.com/media/2b5a3e8dedb2e6c48dc7c79bb35be51f/href</a></iframe><ul><li><strong><em>columns()</em></strong> and <strong><em>from()</em></strong> must be public as they are functions that can be called by any client external to our library;</li><li><strong>columns</strong> and <strong>tableWrapper</strong> should be annotated with <strong><em>@PublishedApi</em></strong> because the functions we are making public, are <strong>inline</strong> and manipulate these properties.</li></ul><p><strong>11.2)</strong> Change the <strong><em>innerJoin()</em></strong> and <strong><em>leftJoin()</em></strong> functions in the <strong><em>TableWrapper</em></strong> class to be public, and change the <strong><em>TableWrapper</em></strong> and <strong><em>JoinWrapper</em></strong> constructor to <strong>@PublishedApi internal</strong>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d1766e5b5e8d5215e52dc38430a17ad5/href">https://medium.com/media/d1766e5b5e8d5215e52dc38430a17ad5/href</a></iframe><ul><li><strong><em>innerJoin()</em></strong> and <strong><em>leftJoin()</em></strong> must be public as they are functions that can be called by any client external to our library;</li><li>the constructor of the <strong><em>TableWrapper</em></strong> and <strong><em>JoinWrapper</em></strong> classes must be <strong><em>internal</em></strong> as they must not be triggered by any client external to our library, and must be annotated with <strong><em>@PublishedApi</em></strong> as they are called by an <strong>inline</strong> function that is public.</li></ul><p><strong>11.3)</strong> Finish adjusting the others:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9e0f47312520cd4d6d0512a9723723a4/href">https://medium.com/media/9e0f47312520cd4d6d0512a9723723a4/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85bdae4c8cb59be4655f4b97c18c4c0/href">https://medium.com/media/b85bdae4c8cb59be4655f4b97c18c4c0/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ee0ea272cc7e30d9893bb93108af70fa/href">https://medium.com/media/ee0ea272cc7e30d9893bb93108af70fa/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5b5ec791806f48698073c5b587f76889/href">https://medium.com/media/5b5ec791806f48698073c5b587f76889/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3dc68e9e16bf99c87001a78638375273/href">https://medium.com/media/3dc68e9e16bf99c87001a78638375273/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c699b188de3924b61cb97b01a7c560b1/href">https://medium.com/media/c699b188de3924b61cb97b01a7c560b1/href</a></iframe><h3><strong>That’s all folks!</strong></h3><p>We used some really cool features that Kotlin provides to write this DSL.</p><p>I hope contributed to your knowledge.</p><p><a href="https://github.com/fabiomirgo/sql-dsl">fabiomirgo/sql-dsl</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fcf215b7bb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>