22 Matching Annotations
  1. Mar 2021
  2. Feb 2021
    1. In combination with [Track()], the :magnetic_to option allows for a neat way to spawn custom tracks outside of the conventional Railway or FastTrack schema.

      Instead of magnetic_to:, I propose wrapping the steps that are on a separate track in something like...

        DefTrack do :paypal do
          step :charge_paypal
        end
      

      or

        paypal_track = RailwayTrack do :paypal do
          step :charge_paypal
        end
      

      so we can reference it from outputs, like we can with tracks created with Path helper.

    2. Output() in combination with Path() allow very simple modelling for alternive routes.
    3. In both filters, you’re able to rename and coerce variables. This gives you a bit more control than the simpler DSL.
    1. Operations define the flow of their logic using the DSL and implement the particular steps with pure Ruby.
  3. Dec 2020
  4. Nov 2020
    1. I'm thinking of creating something similar to a utility-first CSS framework like Tailwind, here's how it could look like:StyledText( style: [selfAlignRight, padding(8), fontSize(20), fontBold], text: 'hello' )
  5. Oct 2020
  6. Apr 2020
    1. no need to learn a new framework it's just Ruby's syntax + new methods and actually that's one of the reasons Google invented a simple and stupid language called Golang instead of a magical one to prevent developers from doing magic and just shipping features instead of playing with DSLs.
  7. Jun 2018
  8. Jul 2017
  9. Jun 2017
    1. internal dsl in java 8 in three ways:

      1. by Method Chaining
      2. by Nested Functions
      3. by Lambda Expression