#Daggerizing Swirly

1 messages · Page 1 of 1 (latest)

rigid oyster
#

Overall it was a great experience, with the following brief stumbles:

#
  • I didn't remember the TypeScript constructor syntax, and searched 'constructor' in our docs trying to find it, forgetting that this is actually called 'entrypoint:' https://docs.dagger.io/manuals/developer/entrypoint-function/
    • We actually call it "constructor" in a sub-header (https://docs.dagger.io/manuals/developer/entrypoint-function/#constructor-only-arguments) so that showed up in my search, but the specific headline didn't seem like what I was looking for. Should probably rename this to be consistent.
    • For me the term 'entrypoint' is associated with containers. The module/function terms are programming related, and I'm in a programming mindset already while writing a module, so 'constructor' is the first word that springs to mind. Don't want to re-litigate old bikesheds, and maybe my brain just never GC'd the old 'constructor' term, but I thought I'd mention this in case other folks stumble on it too.
#
  • The order of Directory.diff threw me off since it breaks the chaining syntax. I think I've run into this multiple times before, including in our own internal usage. I'd suggest flipping it, but that'll be a really subtle breaking change. 😭
#
  • The error output in the TUI was pretty bad; the root cause would tend to be offscreen in my tiny terminal. The good news is the improved error output I'm working on (and actually trying to troubleshoot with Swirly) fixes that.
#

Besides that, smooth sailing! As a TypeScript noob I was able to find everything I needed. Even used the new terminal/debugging feature a lot while trying to figure out what packages I needed to install. (Shout-out to @wanton kraken @misty fossil @real whale)

#

(Sorry, forgot to @silent 😅)