elm/error-message-catalog

Issues

• Type alias should be expanded to show the details

  #331 opened 5 years ago by ChristophP
  2

• No `-- comments` above module: isn't so clear for a beginner?

  #359 opened 9 months ago by badlydrawnrob
  0

• No hint that you've defined a type that you're now confusing with another type

  #358 opened a year ago by willnwhite
  0

• argument order errors overwhelming.

  #357 opened a year ago by sijmenvb
  0

• Bad unicode escape – bad suggestion :)

  #356 opened 2 years ago by lydell
  0

• Compiling an empty model gives unhelpful error message

  #318 opened 5 years ago by dasch
  1

• Trying to use non-exposed constructors

  #355 opened 2 years ago by Janiczek
  0

• Difficulty understanding Type Mismatch error for beginner

  #332 opened 4 years ago by francois
  1

• Debug.todo could report types of the holes

  #354 opened 3 years ago by Janiczek
  0

• better guidance for stack overflows

  #353 opened 3 years ago by dandrake
  0

• Confusing error when attempting to install a pre-0.19 package

  #334 opened 4 years ago by sentience
  1

• An extra space in one of the items in the case statement yields a weird error message

  #352 opened 3 years ago by domenkozar
  0

• Two multiline comments without code between them trigger a parsing error

  #351 opened 4 years ago by pdamoc
  3

• Better error message when attempting Haskell-style pattern matching

  #350 opened 3 years ago by Gaelan
  1

• Confusion between type name and variant name shadowing

  #349 opened 3 years ago by wolfadex
  0

• Subtraction without whitespace gives non-intuitive error

  #348 opened 3 years ago by Strepto
  0

• Record typo suggested fix could be better

  #347 opened 3 years ago by kreibaum
  0

• there should be a hint when swapping arguments

  #346 opened 4 years ago by dullbananas
  0

• Elm repl gives bad error messages for incorrect capitaliztion

  #345 opened 4 years ago by YourFin
  2

• confusing error when running `elm install` on a read-only elm.json

  #344 opened 4 years ago by Zimmi48
  2

• Improve error when using type alias instead of type

  #343 opened 4 years ago by dullbananas
  1

• more informative Maybe error

  #342 opened 4 years ago by Hasimir0
  1

• Error message for UNKNOWN EXPORT

  #341 opened 4 years ago by mokshasoft
  1

• using ^ to indicate position in a line is bad for accessibility

  #312 opened 5 years ago by mikolysz
  3

• Using `Maybe` instead of `Just`

  #340 opened 4 years ago by danfishgold
  1

• Got type X instead of type Y having single variant X

  #339 opened 4 years ago by malaire
  0

• Report of incorrect/extraneous fields should not suggest already present fields

  #338 opened 4 years ago by jfmengels
  0

• Inverted arguments by mistake

  #337 opened 4 years ago by gabriela-sartori
  0

• lambda expression = something is really tripping me up

  #336 opened 4 years ago by dotnetCarpenter
  1

• Naming error when tuple result on lambda has no parens

  #335 opened 4 years ago by reinux
  0

• Decimals starting with `.` have confusing error message.

  #333 opened 4 years ago by openorclose
  0

• Vertical bar error message wrong

  #330 opened 5 years ago by adhedgehog
  0

• Be more specific about port type signature issue

  #329 opened 5 years ago by Janiczek
  0

• Type alias should be expanded or diffed to figure out problematic areas

  #328 opened 5 years ago by j-maas
  0

• unlear (?) error messages when working with tuples

  #327 opened 5 years ago by benkoshy
  2

• When given argument of wrong type, error message is sometimes overzealous in its assumptions about the correct type.

  #326 opened 5 years ago by jmbromley
  0

• Unclear message when elements in list produce non-homogeneous Html values

  #325 opened 5 years ago by ravicious
  1

• Which error messages should exist?

  #320 opened 5 years ago by CSDUMMI
  1

• Generic error message when type alias is missing 'alias'

  #324 opened 5 years ago by ianmackenzie
  0

• Confusing error when main documentation comment comes after import

  #323 opened 5 years ago by TSFoster
  0

• Recursive calls in `let` fail cryptically when using arrays/records

  #322 opened 5 years ago by showell
  1

• error when publishing package with non-root elm.json

  #321 opened 5 years ago by bburdette
  2

• Add line number next to File path separated by a ":"

  #313 opened 5 years ago by girishso
  2

• Confusing error when function that takes "number"s must take "Int"s

  #317 opened 5 years ago by harrysarson
  0

• Adding a plus sign to numbers is not explicit about pluses not being allowed

  #315 opened 5 years ago by ChristophP
  0

• When package.elm-lang.org is not accessible, `elm make` does not tell which dependencies it is trying to fetch

  #314 opened 5 years ago by HenkPoley
  0

• Using "type" instead of "type_"

  #311 opened 5 years ago by lovasoa
  0

• Missing code location for unknown import

  #310 opened 5 years ago by lydell
  0

• Display a warning when no js is emitted

  #309 opened 5 years ago by sebsheep
  0

• Dict should require comparable and Dict.get error messages can be more specific

  #308 opened 5 years ago by showell
  0