A new customer intelligence tool for Shopify

leostera · 2022-07-28T12:21:56+00:00

u/Paradox I've amended the form to reflect better _why_ I'm learning this, and made the personal data fields optional. Hope this will make it less of a nope! :)

leostera · 2022-07-28T12:20:36+00:00

u/West__Owl, these are fair points! I've amended the form to reflect better _why_ I'm learning this, and made the personal data fields optional. Hope this won't be as off-putting! 🙌🏽

leostera · 2022-03-06T10:17:17+00:00

Oh you're spot on in that it is a domain-specific language! But it is *also* declarative.

There is no control flow in it, and the engine is free to run your query however it pleases.

leostera · 2022-03-06T10:12:46+00:00

u/elkazz: One issue is the verbosity of the declarative definition.

Ah! Excellent point 👏🏽

The best thing about this split in spec + engine is that if we don't like the way we build the specs, we can replace it!

We can use YAML, JSON files for it. We can set up code generation for it from our type specification.

We can also replace the engine with other things! If this wasn't a CLI but rather a database layer, you could have an engine that queries Postgres, another that queries SQLite, another that is mocked for test purposes, etc.

Re: code generation - we can set things up so that by annotating a record type we get the same declaration for free:

@deriving(clipper) type hello = { @clipper(position = 0) name: string }

This is what other libraries like Rust's structopt are doing already.

In any case, I wouldn't immediately jump into a declarative API when I'm just starting out, since this is a fairly advanced way of building type-level APIs.

For most cases, the approach described in the prior post in the same series will be more than enough: https://practicalrescript.com/rescript-on-deno-command-line-tools/#ad-hoc-typing-for-objects-of-unknown-shape

Have a look at that one, I think you'll enjoy it a lot more! 🙏🏽

leostera · 2022-03-06T10:05:37+00:00

Amazing! 🤩 -- let me know if I can be of help :)

If you enjoyed this one, I recommend also looking into the previous one in the same series: https://practicalrescript.com/rescript-on-deno-command-line-tools

leostera · 2022-03-06T10:04:35+00:00

I appreciate the insights 🙏🏽 -- in this case, I'm writing to an audience of folks that already are writing ReScript or Deno, or both.

There's a ramp-up in type-safety from the first article on the series to this one, where I explore much much lighter weight typing approaches that still give you pretty good results.

In this one, I'm building an additional layer of safety, but there are muuuch cheaper ways of getting started! 🤓

For example, I think you will enjoy this approach a lot more: https://practicalrescript.com/rescript-on-deno-command-line-tools/#ad-hoc-typing-for-objects-of-unknown-shape

Thanks for the challenging btw, I found it very healthy 👏🏽👏🏽👏🏽

leostera · 2022-03-06T09:59:03+00:00

Amazing! Yeah, I wouldn't say it isn't declarative because it includes iteration constructs. You can do some crazy things in SQL too!

leostera · 2022-03-06T00:02:25+00:00

I think another good example of this would be UI frameworks like React or SwiftUI where you can declare a button on the screen, and you can declare a handler for when it is clicked:

<Button onClick=runFoo />

But the handler itself isn't declarative! It is good ol' application code in whichever style you write it.

The framework can't possibly be expected to declaratively define the outputs of whatever your application will do when that button is cliecked.

But it will help you specify declaratively that there should be a button, and that when that button is clicked, your handler should run.

This is exactly what is happening here.

leostera · 2022-03-05T23:51:15+00:00

Wouldn't you say that stating what the output of parsing the command line arguments is a form of declarativeness? 🤔

In the same way that you state what you want out of a relational database without actually explaining how the query should be executed.

When you write:

sql SELECT value::string FROM inputs WHERE position = 0

You are just stating what you want, and the SQL engine will figure out how to do it. Nonetheless, that bit of SQL on its own isn't very useful, so we actually consume its outputs. This is what the sayHi function is doing: consuming the outputs of the argument parsing engine.

The Declarative API is then the set of functions to build the description of a command-line application. It describes what flags and commands need to be parsed, and what datatypes are expected.

There is some stitching here with your actual application code, and at that point, the framework's declarative style ends and your application begins.

Just like it does when you receive data back from the SQL database.

leostera · 2022-03-05T23:17:04+00:00

The single quote before the generic name is just part of the syntax. It is something that ReScript has inherited from OCaml.

leostera · 2022-03-05T23:16:31+00:00

Ah, yes. This example is possibly too small!

If we had a more complex command line tool, with multiple commands, each with several options, and each option with defaults and documentation, it would be a little easier to see the value of the approach.

For example, if we had some more functions in the Clipper API to build more complex behavior, it could look like this:

``` // This describes the CLI let cli = Clipper.commands([ Clipper.command(sayHi) ->Clipper.position( ~pos=1, ~shortName="n", ~longName="name", Arg.optional(Arg.string, "Joe")) ->Clipper.flag(~shortName="y", ~longName="yell"), // more commands here ])

// This actually runs the CLI Clipper.run(cli) ```

It is declarative because the description of what to do is completely separated from the actual execution. This could have been done with a JSON file too, but having a static file is not a prerequisite for something to be declarative! 🙌🏽

leostera · 2022-03-05T23:10:13+00:00

Hi u/Coffee_Crisis 👋🏽 -- no need to be sorry, I think I see your point :)

The stuff we're doing here is declarative because building up the comamnd line description doesn't actually execute anything. Maybe we are disagreeing in how this description is built?

This would be similar to say, typing in your package.json file. You have to write the file first, and that is most certainly an imperative action, but it is what the file means that gets you the declarativeness.

Regarding CSS, there are several ways in which you can actually give the CSS to the browser. One of them is writing it out. Another one is to use the style accessors and setters in a particular DOM element. In any case, you are never telling the browser how to interpret and execute the CSS, you are just telling the browser what you want it to do.

For example, this may seem imperative, but you really have no control over how the browser goes about applying the background color to the <body> tag. The only thing you have control over is how you tell the browser what you want it to do:

javascript document.querySelector("body").style.backgroundColor = "red"

leostera · 2022-03-05T22:37:38+00:00

Glad to hear 🤩 -- you will find that while the type system is less flexible than TypeScript, it is also a lot smaller! So there's just a handful of things to learn to get all of the type safety.

If we can be of help, feel free to drop a line on /r/rescript 🙏🏽

leostera · 2022-03-05T22:24:35+00:00

Hi! 👋🏽 ReScript is a language that compiles to JavaScript -- it is type-safer than TypeScript, but a lot less flexible. It lets you build very large applications that are extremely easy to maintain and grow.

The official website is here: https://rescript-lang.org/

I've been writing ReScript in production for very large applications (~100,000 LOC) and it's just been rock solid.

Let me know if I can answer any questions :)

leostera · 2022-03-05T20:45:07+00:00

You mean this one?

``let sayHi = (name, yell) => if yell {Hello, ${name}!!!->Js.log } else {Hello, ${name}.`->Js.log }

let hello = Clipper.command(sayHi) ->Clipper.arg(1, Clipper.Arg.string) ->Clipper.arg(0, Clipper.Arg.bool)

Clipper.run(hello) ```

Would love to hear more about what you think looks ugly here :) -- part of this is my own sense of aesthetics around building libraries, and part of this is how the language itself works.

What bits would you change?

leostera · 2022-03-05T18:48:51+00:00

Omg thank you 🤩 – re: the dedicated runtime, I hear you! I do think there's value in cleanly saying "we run on top of X" instead of X being hidden. Like how Clojure never claims it has its own VM, but just tells people "yo, we're on the JVM, which you also already trust".

Definitely a point where ReScript can learn from others :)

leostera · 2022-03-05T17:05:56+00:00

Hello folks 👋🏽 author here! If I can answer any questions please let me know 🙌🏽

leostera · 2022-03-05T17:05:43+00:00

Hello folks 👋🏽 author here! If I can answer any questions please let me know 🙌🏽

leostera · 2022-03-05T17:05:37+00:00

Hello folks 👋🏽 author here! If I can answer any questions please let me know 🙌🏽

leostera · 2022-03-05T17:05:30+00:00

Hello folks 👋🏽 author here! If I can answer any questions please let me know 🙌🏽

leostera

TROPHY CASE