Make highlighting of `module` line more permissive

[evancz]

One of the changes on the table for 0.17 is the following tweak to module declarations:

-- OLD
module Foo (a, b, c) where

-- NEW
module Foo exposing (a, b, c)

The current syntax highlighting freaks out if there is no where at the end and messes up highlighting for the whole file. Is there any way it can be made more flexible in the lead up to 0.17 just for me? Like is there something I can tweak locally even?

I currently have to do module Whatever exposing (..) -- where to make both Elm and the syntax highlighter happy, which is doable, but I risk checking this kind of weird thing in.

[deadfoxygrandpa]

OK, thanks for the heads up. I'll change this very soon.

On Thu, Apr 7, 2016 at 4:58 AM, Evan Czaplicki notifications@github.com wrote:

One of the changes on the table for 0.17 is the following tweak to module declarations:

-- OLDmodule Foo (a, b, c) where -- NEWmodule Foo exposing (a, b, c)

The current syntax highlighting freaks out if there is no where at the end and messes up highlighting for the whole file. Is there any way it can be made more flexible in the lead up to 0.17 just for me? Like is there something I can tweak locally even?

I currently have to do module Whatever exposing (..) -- where to make both Elm and the syntax highlighter happy, which is doable, but I risk checking this kind of weird thing in.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/deadfoxygrandpa/Elm.tmLanguage/issues/99

[mordrax]

module CounterPair exposing (init, update, view) --where Workaround until PR is merged