
Episode 64
064: Projects We Wish We Had Time For
We discuss the power of the Elm when paired with developer tools, and we go through our notes to look at Elm tools we wish we had the time to build.
August 29, 20221h 21m
Audio is streamed directly from the publisher (cdn.simplecast.com) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
Sponsor: CareRev
CareRev is looking for Senior Frontend Elm engineers (job listing).
elm-review-simplify- Elm Radio Root Cause of False Positives episode
- Dillon's pairing session using snapshot testing prototype with Corey Haines
elm-snapshot-testprototype repo- Approval testing
elm-coverageelm-instrument- Llewellyn Falco Gilded Rose kata video
- Idea: intellij integration for
elm-coverage - Idea: code actions for safe refactorings
- Idea: elm-review integration in intellij
- Idea:
sparksp/elm-review-importseither new feature, or separate project to give suggestions to make all inconsistent imports in a project consistent - Idea:
elm-reviewcode actions - Idea:
elm-reviewcollection mechanism to gather data from an AST - Pairwise testing (or all pairs)
- Idea: pairwise permutation API that minimizes the number of permutations to go through to get complete coverage
- Idea: mutation testing tool for Elm (is Phillip's tool relevant here?)
- Idea: generated API for
elm-graphqlbut with factory-style API for mocking out data that is compliant to the graph schema, for use with things likeelm-program-test - Idea:
Browser.applicationwrapper that provides some common initial flags like start time, initial window dimensions etc - Idea: HTTP Error type to get bad status payload that can be shared between libraries to reuse the same type (similar to the
HttpErrortype defined inelm-graphql) - Aaron's community-standard
elm-colorpackage - Idea: tool to automatically vendor or un-vendor Elm packages
- Idea:
elm-formatin Elm - Idea:
elm diff, but it gives you more detailed information about code changes even if they don't change the API - Idea: Phantom Builder analyzer that generates a state diagram from Elm code
- Idea: suggest types based on what's possible in your current editor context
- Idea: type inference and value inference in
elm-review - elm-http-fusion
- Idea: use a collection of HTTP requests to an endpoint in
elm-http-fusionto gather better type incormation about an API - Idea: make tools like
elm-http-fusionembeddable in the elm-pages dev server so you can interactively fix decoder errors, etc. - Idea: elm-pages dev server code actions from the UI, like scaffolding new routes
- elm-codegen
- Idea: use
elm-codegenfor elm-pages scaffolding for user-customizable templates - Official Elm blog post The Syntax Cliff
- Idea: show ANSI color code error messages embedded in blog posts
- Talk about the Hedy language: What every programmer should know about cognition by Felienne Hermans
- Elm Guide translated into French
- Idea: translatable error messages and language keywords for Elm
- Idea:
elm-csstool to make inline styles into static CSS files and replace the styles with a reference to the generated class. Goal: reduce bundle size and performance overhead - Idea: codemod tool to post-process Elm code using
elm-reviewfixes in a hidden temp directory - Idea: Elm step debugger
- Idea:
elm/parserdebugger to see the state machine of what has been consumed - Idea: Elm debugger improvements like filtering Msg types, customizable inspecting for certain types
- Idea: inspectable
Cmds in the debugger, or similar idea for debuggingelm-pagesDataSources to see why a failure happened and what the breadcrumbs are - Idea: React
ink, but for Elm awesome-elm-sponsorshiprepo