Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments may cause parsing failure #92

Closed
muelli opened this issue Dec 10, 2017 · 1 comment
Closed

Comments may cause parsing failure #92

muelli opened this issue Dec 10, 2017 · 1 comment

Comments

@muelli
Copy link

muelli commented Dec 10, 2017

I'm coming from dillonkearns/elm-typescript-interop#3 and it seems that the elm-ast package fails to parse

port module Main exposing (..)


init location =
    let
        currentRoute =
            Routing.parseLocation location
    in
        --( initialModel currentRoute, fetchUser )
        ( initialModel currentRoute, Cmd.batch
                                            [ check "yo"
                                            , fetchUser
                                            ]  )

with

Err ((),{ data = "port module Main exposing (..)\n\n\ninit location =\n let\n currentRoute =\n Routing.parseLocation location\n in\n --( initialModel currentRoute, fetchUser )\n ( initialModel currentRoute, Cmd.batch\n [ check \"yo\"\n , fetchUser\n ] )\n\n", input = "init location =\n let\n currentRoute =\n Routing.parseLocation location\n in\n --( initialModel currentRoute, fetchUser )\n ( initialModel currentRoute, Cmd.batch\n [ check \"yo\"\n , fetchUser\n ] )\n\n", position = 33 },["expected end of input"])
@wende
Copy link
Collaborator

wende commented Dec 10, 2017

Duplicate of #41

@wende wende marked this as a duplicate of #41 Dec 10, 2017
@wende wende closed this as completed Dec 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants