I’m working on making a Route type which can be used throughout my project to refer to the possible routes in my frontend and convert them to/from URLs. A common sanity check/test for this kind of thing is to try “round-tripping” routes through the to-URL/from-URL functions to ensure everything is c…

I think the established pattern at this point is using a reminder, just like you said. That is also what we used to do at my workplace. Now, we use a custom elm-review rule instead. By convention, we consider all values that look like allXyz : List Xyz to need to have all the constructors of the ty…

The reminder-function is the only thing that works AFAIK. There was a proposal: [image] `enumerate` function for non-infinite custom types - proposal Request Feedback tl;dr I propose the compiler would expose a “magical” function enumerate : Type a -> List a (for lack of …

Thanks, this seems like a great use of elm-review.

Covering all constructors

Learn

ni-ko-o-kin March 13, 2020, 8:03am 3

The reminder-function is the only thing that works AFAIK.

There was a proposal:

Topic		Replies	Views
Typesafe Url.Parser.oneOf usage? Learn	10	1361	September 17, 2018
NoMissingTypeConstructor elm-review rule fix Request Feedback	3	1155	February 24, 2022
Extracting type metadata from Elm code? Learn	18	2019	September 16, 2020
A tool to generate a list of custom type constructors Request Feedback	6	1359	February 5, 2019
Elm-test-tables; a collection of useful elm-test extensions Show and Tell	0	853	May 25, 2018

Covering all constructors

Related topics