Importing Metabase project results in bogus "profiles"

[jeff303]

When importing metabase, it seems that Cursive detects a bunch of bogus profiles. Looks to be some kind of parsing problem. Example screenshot here:

[cursive-ide]

The problem with this is the composite profiles, which contain both keywords and maps:

   :run-with-repl
   [:exclude-tests
    :include-all-drivers

    {:env
     {:mb-jetty-join "false"}

     :repl-options
     {:init    (do (require 'metabase.core)
                   (metabase.core/-main))
      :timeout 60000}}]

I've never seen maps used in composite profiles before. The documentation doesn't say this is allowed, but then hints that it might be but says not to mix them:

It is not recommended to make a composite profile which contains both keywords and maps; they should either be all keywords or all maps.

Anyway, this will be fixed for the next build.