Skip to content

Explain import early on guide.elm-lang.org #883

Open
@MatthewCroughan

Description

@MatthewCroughan

The import keyword seems magical. As a newcomer to Elm, I read https://korban.net/posts/elm/2019-11-17-elm-ui-introduction/, it explains that I should:

  1. elm install mdgriffith/elm-ui
  2. import Element exposing (..)

From these two steps, as a noob, I cannot possibly understand that Element is actually something that is derived from the src folder of elm-ui, other than by going to the Slack/Matrix channels and asking the question "Where does Element come from?"

ls ~/.elm/0.19.1/packages/mdgriffith/elm-ui/1.1.8/src/
Element  Element.elm  Internal

It would be helpful if the elm-guide could explain the import keyword early on, so that I can understand where import is searching for module names.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions