The latest articles on DEV Community by Cyril Kato (@cyri_). https://dev.to/cyri_ https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F189132%2F9e260e52-905b-426f-a9eb-1f81bdc93ad1.png https://dev.to/cyri_ en Cyril Kato Wed, 31 May 2023 18:56:03 +0000 https://dev.to/sashite/an-open-source-tool-for-board-games-3g91 https://dev.to/sashite/an-open-source-tool-for-board-games-3g91 <p>We are pleased to announce the release of <strong><a href="https://github.com/sashite/qi.rb" rel="noopener noreferrer">Qi.rb</a></strong> 10.0.0, a flexible and robust tool designed to represent board game positions for various games, including Chess, Makruk, Shogi, or Xiangqi, among others.</p> <p>Qi is game-agnostic, providing a flexible framework to represent a wide range of game states. It captures essential game details, including the pieces in play, their arrangement on the board, the sequence of turns, and other game-specific states. </p> <p>One of the key features of Qi is its ability to manipulate and update game states via the 'commit' method, enabling smooth transitions between game states. The tool also incorporates an 'eql?' method for comparing different game states, useful for tracking game progress, detecting repeats, or even facilitating AI development for games.</p> <p>In addition to these, Qi keeps track of the sequence of turns, providing an efficient way to manage game progress. The tool also provides access to game-specific data, such as the current arrangement of pieces on the board (<code>squares_hash</code>) and the pieces captured by each player (<code>captures_hash</code>). This information is key to understanding the current status of the game.</p> <p>Finally, Qi is customizable and adaptable to your specific needs. The keys and values in <code>captures_hash</code> and <code>squares_hash</code>, as well as the items in <code>turns</code> and the values in <code>state</code>, can be any type of object.</p> <p>While Qi does not generate game moves itself, it serves as a reliable foundation upon which game engines can be built. Its primary focus is on providing a robust and adaptable representation of game states, thus fostering the development of diverse board game applications.</p> <p>We look forward to seeing the innovative ways in which the community will use and build upon <a href="https://rubygems.org/gems/qi/versions/10.0.0" rel="noopener noreferrer">Qi 10.0.0</a>. For more details and to get started with Qi, visit our <a href="https://github.com/sashite/qi.rb" rel="noopener noreferrer">open source project page</a>.</p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3y1ziqk3255w9j8r3ky4.jpeg" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3y1ziqk3255w9j8r3ky4.jpeg" alt=" " width="800" height="800"></a></p> shogi chess xiangqi gamedev Cyril Kato Sat, 03 Jul 2021 11:39:46 +0000 https://dev.to/cyri_/what-ruby-code-to-expect-from-a-testing-dsl-4oe1 https://dev.to/cyri_/what-ruby-code-to-expect-from-a-testing-dsl-4oe1 <p>Have you ever wondered what the Ruby code generated by your test DSL might look like?</p> <p>As a developer, it might be interesting to know. Maybe it's so horrible that it's impossible to write directly. Or maybe it's even lighter than a minitest test set. Who knows?</p> <p>To try to answer this question while avoiding the endless debate between RSpec and minitest, I will use the <a href="https://r-spec.dev/" rel="noopener noreferrer">RSpec clone</a> project for the purpose of this post.</p> <h2> What is RSpec clone? </h2> <p>It is a minimalist reimplementation of RSpec that emphasizes correctness, security and standardization.</p> <p>Driven by the desire to enforce the guidelines and best practices outlined in the community <a href="https://rspec.rubystyle.guide/" rel="noopener noreferrer">RSpec style guide</a>, this RSpec clone includes most of RSpec’s DSL to express expected outcomes with no magical powers.</p> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2fql5u6s7x1uw08qnr27.jpg" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2fql5u6s7x1uw08qnr27.jpg" alt="What did you RSpec?" width="800" height="523"></a></p> <p>Without further ado, here are some correspondences between the DSL syntax and the generated Ruby code to understand how the framework builds and executes tests. For ease of reading, these mappings are grouped by method.</p> <h2> From DSL to Ruby </h2> <h3> <code>describe</code> method </h3> <p>When I write this,<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">RSpec</span><span class="p">.</span><span class="nf">describe</span> <span class="no">String</span> <span class="k">do</span> <span class="k">end</span> </code></pre> </div> <p>I expect this code to be generated:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">Class</span><span class="p">.</span><span class="nf">new</span> <span class="k">do</span> <span class="kp">private</span> <span class="k">def</span> <span class="nf">described_class</span> <span class="no">String</span> <span class="k">end</span> <span class="k">end</span> </code></pre> </div> <h3> <code>context</code> method </h3> <p>When I write this,<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">RSpec</span><span class="p">.</span><span class="nf">context</span> <span class="s2">"when in a context"</span> <span class="k">do</span> <span class="k">end</span> </code></pre> </div> <p>I expect this code to be generated:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">Class</span><span class="p">.</span><span class="nf">new</span> <span class="k">do</span> <span class="k">end</span> </code></pre> </div> <h3> <code>subject</code> method </h3> <p>When I write this,<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">RSpec</span><span class="p">.</span><span class="nf">describe</span> <span class="s2">".subject"</span> <span class="k">do</span> <span class="n">subject</span> <span class="k">do</span> <span class="s2">"foo"</span> <span class="k">end</span> <span class="k">end</span> </code></pre> </div> <p>I expect this code to be generated:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">Class</span><span class="p">.</span><span class="nf">new</span> <span class="k">do</span> <span class="kp">private</span> <span class="k">def</span> <span class="nf">subject</span> <span class="s2">"foo"</span> <span class="k">end</span> <span class="k">end</span> </code></pre> </div> <h3> Embedded <code>describe</code> method </h3> <p>When I write this,<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">RSpec</span><span class="p">.</span><span class="nf">describe</span> <span class="s2">".describe"</span> <span class="k">do</span> <span class="n">describe</span> <span class="s2">"embedded describe"</span> <span class="k">do</span> <span class="k">end</span> <span class="k">end</span> </code></pre> </div> <p>I expect this code to be generated:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="n">base</span> <span class="o">=</span> <span class="no">Class</span><span class="p">.</span><span class="nf">new</span> <span class="k">do</span> <span class="k">end</span> <span class="no">Class</span><span class="p">.</span><span class="nf">new</span><span class="p">(</span><span class="n">base</span><span class="p">)</span> <span class="k">do</span> <span class="k">end</span> </code></pre> </div> <h3> <code>let</code> method </h3> <p>When I write this,<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">RSpec</span><span class="p">.</span><span class="nf">describe</span> <span class="s2">".let"</span> <span class="k">do</span> <span class="n">let</span><span class="p">(</span><span class="ss">:answer_to_everything</span><span class="p">)</span> <span class="p">{</span> <span class="mi">41</span> <span class="o">+</span> <span class="n">one</span> <span class="p">}</span> <span class="n">let</span><span class="p">(</span><span class="ss">:one</span><span class="p">)</span> <span class="p">{</span> <span class="mi">1</span> <span class="p">}</span> <span class="k">end</span> </code></pre> </div> <p>I expect this code to be generated:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">Class</span><span class="p">.</span><span class="nf">new</span> <span class="k">do</span> <span class="kp">private</span> <span class="k">def</span> <span class="nf">answer_to_everything</span> <span class="mi">41</span> <span class="o">+</span> <span class="n">one</span> <span class="k">end</span> <span class="k">def</span> <span class="nf">one</span> <span class="mi">1</span> <span class="k">end</span> <span class="k">end</span> </code></pre> </div> <h3> <code>before</code> method </h3> <p>When I write this,<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">RSpec</span><span class="p">.</span><span class="nf">describe</span> <span class="s2">".before"</span> <span class="k">do</span> <span class="n">before</span> <span class="k">do</span> <span class="nb">puts</span> <span class="s2">"hello"</span> <span class="k">end</span> <span class="k">end</span> </code></pre> </div> <p>I expect this code to be generated:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">Class</span><span class="p">.</span><span class="nf">new</span> <span class="k">do</span> <span class="kp">private</span> <span class="k">def</span> <span class="nf">initialize</span> <span class="nb">puts</span> <span class="s2">"hello"</span> <span class="k">end</span> <span class="k">end</span> </code></pre> </div> <h3> <code>expect</code> method </h3> <p>When I write this,<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">RSpec</span><span class="p">.</span><span class="nf">describe</span> <span class="s2">"#expect"</span> <span class="k">do</span> <span class="n">it</span> <span class="p">{</span> <span class="n">expect</span><span class="p">(</span><span class="mi">41</span><span class="p">.</span><span class="nf">next</span><span class="p">).</span><span class="nf">to</span> <span class="n">be</span><span class="p">(</span><span class="mi">42</span><span class="p">)</span> <span class="p">}</span> <span class="k">end</span> </code></pre> </div> <p>I expect this code to be generated:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="n">description</span> <span class="o">=</span> <span class="no">Class</span><span class="p">.</span><span class="nf">new</span> <span class="k">do</span> <span class="k">end</span> <span class="nb">require</span> <span class="s2">"matchi/rspec"</span> <span class="nb">require</span> <span class="s2">"r_spec/clone/expectation_target"</span> <span class="n">example</span> <span class="o">=</span> <span class="no">Class</span><span class="p">.</span><span class="nf">new</span><span class="p">(</span><span class="n">description</span><span class="p">)</span> <span class="p">{</span> <span class="kp">include</span> <span class="no">Matchi</span><span class="o">::</span><span class="no">Helper</span> <span class="p">}</span> <span class="n">sandbox</span> <span class="o">=</span> <span class="n">example</span><span class="p">.</span><span class="nf">new</span> <span class="n">sandbox</span><span class="p">.</span><span class="nf">instance_eval</span> <span class="p">{</span> <span class="no">ExpectationTarget</span><span class="o">::</span><span class="no">Value</span><span class="p">.</span><span class="nf">new</span><span class="p">(</span><span class="mi">41</span><span class="p">.</span><span class="nf">next</span><span class="p">).</span><span class="nf">to</span> <span class="n">be</span><span class="p">(</span><span class="mi">42</span><span class="p">)</span> <span class="p">}</span> </code></pre> </div> <p>And I expect to see this result in console:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>Success: expected to be 42. </code></pre> </div> <h2> Happy testing with Ruby </h2> <p>Unless <a href="https://github.com/fixrb/brutal" rel="noopener noreferrer">you don't write tests</a>, the advantage of using such DSL interface is to limit the introduction of additional logic in to the specification document with potential errors, to encourage the use of good Ruby patterns with low algorithmic complexity, and to make Ruby code shorter and more (machine) readable.</p> <p><a href="https://speakerdeck.com/ahawkins/bow-before-minitest" rel="noopener noreferrer">According to Adam Hawkins</a>,</p> <blockquote> <p>Rspec is a testing DSL. MiniTest is ruby.</p> </blockquote> <p>I love both, and I hope you'll like <a href="https://r-spec.dev/" rel="noopener noreferrer">RSpec clone</a> too.</p> ruby rspec minitest testing Cyril Kato Sat, 03 Jul 2021 08:51:23 +0000 https://dev.to/cyri_/language-negotiation-with-ruby-5166 https://dev.to/cyri_/language-negotiation-with-ruby-5166 <p>Our world, with its vast array of languages, is a melting pot of diverse cultures and histories. Linguistic diversity is a remarkable aspect of human society that underscores our uniqueness. Just as the web is an intricate network of hyperlinks that binds web pages together, languages interconnect humanity. This myriad of human languages is innumerable, yet the <a href="https://tools.ietf.org/html/bcp47" rel="noopener noreferrer">BCP 47 specification</a> helps us identify and code them by their name, regional variation, and script.</p> <p>In the realm of web services, the <a href="https://tools.ietf.org/html/rfc2616#section-14.4" rel="noopener noreferrer"><code>Accept-Language</code> HTTP header</a> field articulates client preferences concerning languages.</p> <p>Consider a Japanese user, a native speaker who has adjusted their browser settings to receive content primarily in Japanese. This preference is reflected in the following request:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight http"><code><span class="err">Accept-Language: ja </span></code></pre> </div> <p>Suppose this user is from Osaka and has a preference for the Kansai dialect. The parameter can be fine-tuned as follows:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight http"><code><span class="err">Accept-Language: ja-KS, ja;q=0.9 </span></code></pre> </div> <p>Further, let's assume the user has a basic understanding of Thai, but only in the Latin script. The request now becomes:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight http"><code><span class="err">Accept-Language: ja-KS, ja;q=0.9, th-Latn;q=0.8 </span></code></pre> </div> <p>Lastly, let's presume the user is open to other languages, except French and English:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight http"><code><span class="err">Accept-Language: ja-KS, ja;q=0.9, th-Latn;q=0.8, *;q=0.1 fr;q=0, en;q=0 </span></code></pre> </div> <p><a href="https://www.ruby-lang.org/" rel="noopener noreferrer">Ruby</a> offers a compact and handy library, <a href="https://rubygems.org/gems/accept_language" rel="noopener noreferrer"><code>accept_language</code></a>, that simplifies language negotiations between the client and server.</p> <p>If a server, for instance, has translations in Japanese and Korean for a certain resource, the <code>accept_language</code> library can find a common ground between the user's preferred languages and those supported by the application:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="no">AcceptLanguage</span><span class="p">.</span><span class="nf">parse</span><span class="p">(</span><span class="s2">"ja-KS, ja;q=0.9, th-Latn;q=0.8, *;q=0.1 fr;q=0, en;q=0"</span><span class="p">).</span><span class="nf">match</span><span class="p">(</span><span class="ss">:ko</span><span class="p">,</span> <span class="ss">:ja</span><span class="p">)</span> <span class="c1"># =&gt; :ja</span> </code></pre> </div> <p>In the context of a <a href="https://rubyonrails.org/" rel="noopener noreferrer">Rails</a> application, the usage might look like this:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight ruby"><code><span class="c1"># app/controllers/application_controller.rb</span> <span class="k">class</span> <span class="nc">ApplicationController</span> <span class="o">&lt;</span> <span class="no">ActionController</span><span class="o">::</span><span class="no">Base</span> <span class="n">before_action</span> <span class="ss">:best_locale_from_request!</span> <span class="k">def</span> <span class="nf">best_locale_from_request!</span> <span class="no">I18n</span><span class="p">.</span><span class="nf">locale</span> <span class="o">=</span> <span class="n">best_locale_from_request</span> <span class="k">end</span> <span class="k">def</span> <span class="nf">best_locale_from_request</span> <span class="k">return</span> <span class="no">I18n</span><span class="p">.</span><span class="nf">default_locale</span> <span class="k">unless</span> <span class="n">request</span><span class="p">.</span><span class="nf">headers</span><span class="p">.</span><span class="nf">key?</span><span class="p">(</span><span class="s2">"HTTP_ACCEPT_LANGUAGE"</span><span class="p">)</span> <span class="n">string</span> <span class="o">=</span> <span class="n">request</span><span class="p">.</span><span class="nf">headers</span><span class="p">.</span><span class="nf">fetch</span><span class="p">(</span><span class="s2">"HTTP_ACCEPT_LANGUAGE"</span><span class="p">)</span> <span class="n">locale</span> <span class="o">=</span> <span class="no">AcceptLanguage</span><span class="p">.</span><span class="nf">parse</span><span class="p">(</span><span class="n">string</span><span class="p">).</span><span class="nf">match</span><span class="p">(</span><span class="o">*</span><span class="no">I18n</span><span class="p">.</span><span class="nf">available_locales</span><span class="p">)</span> <span class="c1"># If the server cannot serve any matching language,</span> <span class="c1"># it can theoretically send back a 406 (Not Acceptable) error code.</span> <span class="c1"># But, for a better user experience, this is rarely done and more</span> <span class="c1"># common way is to ignore the Accept-Language header in this case.</span> <span class="k">return</span> <span class="no">I18n</span><span class="p">.</span><span class="nf">default_locale</span> <span class="k">if</span> <span class="n">locale</span><span class="p">.</span><span class="nf">nil?</span> <span class="n">locale</span> <span class="k">end</span> <span class="k">end</span> </code></pre> </div> <p>Here's to the joy of linguistic diversity! Let's embrace the challenge of matching as many languages as possible. Happy coding!</p> ruby acceptlanguage http request