I think https://github.com/elm-lang/error-message-catalog/issues is the place for the error message.
On Monday, July 11, 2016 at 10:56:05 PM UTC+1, Nick H wrote: > > Please do not make a new thread to list them all. Most of them are likely > to have been brought up before. > > The most useful place for quality issues to be brought up is in the Github > issue tracker for the relevant project (in the example you mention above, > check the elm compiler project <https://github.com/elm-lang/elm-compiler/>.) > But before posting the issue, do a search to see if it has been raised > before, and what the current status is. > > This mailing list also has a long history. Search for the topics you are > interested in <https://groups.google.com/forum/#!forum/elm-discuss> to > see what people have discussed in the past. If you want to continue an old > discussion, you can start a new thread, but try to build on what has > already been said. > > The best threads are the ones that focus on a single topic. If you have > multiple things to bring up, start multiple threads. > > On Mon, Jul 11, 2016 at 2:41 PM, John Bugner <[email protected] > <javascript:>> wrote: > >> If you have taken the time to learn Elm to a level where you start to >>> understand its core values >>> >> I think I'm already at that point. I like that Elm values simplicity and >> clarity, even if it means bucking the current convention. For example, I >> think switching from the Haskellian keywords 'data' and 'type' to the more >> obvious keywords 'type' and 'type alias' was a move in the right direction. >> Talking about Haskell, I've explained to people before that 'data' defines >> a type and 'type' defines an alias, and it always confused them a little. >> ("Why doesn't 'type' just define a type?" they say.) Sure, it's too late to >> change it in Haskell now, but at least Elm got it right! >> >> I like that Evan has put so much effort into making the compiler give >> useful descriptions of errors and how to resolve them. But, I ran into this >> unhelpful error message the other day: >> >> I need whitespace, but got stuck on what looks like a new declaration. >> You are >> either missing some stuff in the declaration above or just need to add >> some >> spaces here: >> >> 3| import ModuleToImport >> ^ >> I am looking for one of the following things: >> >> whitespace >> >> >> But what caused the error? Not the lack of whitespace! I just forgot to >> add an 'exposing' clause to 'module' declaration. Sure, the error says "You >> are >> either missing some stuff in the declaration above", but it mentions >> needing whitespace three times, and needing an 'exposing' clause zero >> times. I could see a newbie to Elm getting confused and stuck on this error >> because of the unhelpful error message. I admit though that I'm not >> familiar with Elm's compiler, so I don't know how easy or hard it would be >> to change the error message, and what other situations it would affect. >> >> I have many other thoughts for small improvements like this. Should I >> simply make a new thread that lists them all? I fear a bit that people >> will think that I'm just splitting many petty hairs though. >> >> regarding (2) if one creates a project that follows the [elm packages >> guidelines](http://package.elm-lang.org/help/design-guidelines) all they >> have to do is just publish it and wait a little bit for the caches of the >> website to refresh. >> After publishing a package, you are able to use it (install it with >> elm-package) but it take a little bit of time until it is listed as a valid >> package. >> >> Also, concerning (2), >> https://github.com/elm-lang/elm-package/blob/master/README.md#publishing-packages >> >> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Felm-lang%2Felm-package%2Fblob%2Fmaster%2FREADME.md%23publishing-packages&sa=D&sntz=1&usg=AFQjCNGMkDu9pPtmnqdtUHLMF0koHphlTA> >> >> >> Thank you, I will read those pages and try it out. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Elm Discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
