elm-review VS elm-spa-example

It uses devbox, Elm 0.19.1, the latest Elm packages (in particular elm/http 2.0.0), elm-review, Caddy, a sprinkle of Dart Sass, and a handful of Bash scripts (one of them being a deployment script). It uses elm test and features tests for key data structures.

A special shout out to Elm review which has inspired how reanalyze reports code that's transitively dead.

The Elm community has an unofficial linter (called elm-review), which can be used to check your code for potential bugs or mistakes, or highlight a better way to write Elm. Unlike elm-format (and more similar to tools like ESLint), elm-review does not come with any default rules to follow:

elm-review: https://package.elm-lang.org/packages/jfmengels/elm-review/latest/

Glad to see more posts on Elm out there, it really is a great language and ecosystem! Like any large project, it has some issues, but in my day-to-day writing code I have never had as much fun, or had as much confidence that my code does what it says on the tin, as I have with Elm.

I wanted to give a shout out to one of Jeroen's other projects in the Elm ecosystem, elm-review (https://package.elm-lang.org/packages/jfmengels/elm-review/l...), it is an excellent linter/fixer and allows writing your own rules as well.

For technical debt and other code-base maintenance, I'd suggest using elm-review.

About 7 years ago, in the midst of writing Elm in Action, Richard Feldman developed rtfeldman/elm-spa-example, wrote Tour of an Open-Source Elm SPA and graciously shared both of them with the Elm community. The community's response was overwhelmingly positive and it was clear that he had addressed a major need. If you were one of the many web application developers asking "Where can I find an open-source example of an Elm Single Page Application?", then, the Elm SPA Example instantly became the canonical example that everyone was going to point you towards. This was a landmark achievement in the history of Elm.

One accidentally nice thing about that book is the elm version is still the same, so everything is still relevant. As for the SPA, I think the book had to keep things simple, but you'd probably want to look into the author's elm-spa-example next, there's a talk on youtube that goes along with that and he also also a related course on frontend maters worth exploring.

I'm following along with the update behavior of https://github.com/rtfeldman/elm-spa-example/blob/master/src/Main.elm. But I'm not sure how I propagate a message from Main.elm to User.elm to Table.elm (or deeper). How do you manage Msg passing like this?

I am building my first Elm app just following the docs from the official web site. I don't see any direct mention of styling there. Looking around, I see the elm-ui project is one, elm-css is another approach, and the example SPA that Richard Feldman made just uses a stylesheet from Bootstrap, i.e., just plain CSS. If it exists, what's the canonical way of styling an app?

A good example of this is the Elm-SPA example from Feldman: the Main.elm file is basically just glue code for the rest of the project (https://github.com/rtfeldman/elm-spa-example/blob/master/src/Main.elm).

After all that I've managed to reach my goal of being able to run Richard Feldman's Elm SPA Example in my system! 😃 Here's a working implementation compiled to WebAssembly. And for comparison, you can also check out the same code compiled to JavaScript. (Unfortunately the publicly available APIs don't seem to be returning very much data at the moment but there's not much I can do about that!)

Looking at the Real World application I could see that there were better ways to structure my modules using nested TEAs and keeping the Main module as a hub for everything in the app.

If you want to see Elm code, you might look for example projects on GitHub. (https://github.com/rtfeldman/elm-spa-example comes to mind.)

https://github.com/rtfeldman/elm-spa-example is a good example app. I'd also recommend https://codebase.show/projects/realworld in general if you're looking for example apps in various frameworks and languages. I sadly can't share anything from work as it's all private.

- How to properly structure the project. I differentiate between my core utils and the actual gui. Iced states in the documentation that it's inspired by the Elm architecture. So naturally I've read a little bit about the proposed Elm project structure. So I basically end in a structure like this spa example directory recommended by the Elm communicty: Repo