From 3325fdb67d416ad67128307e8e909f598d6ddcde Mon Sep 17 00:00:00 2001 From: Mitchell Hanberg Date: Wed, 8 May 2019 22:05:31 -0400 Subject: [PATCH] Remove comments from config file --- config/config.exs | 29 +---------------------------- 1 file changed, 1 insertion(+), 28 deletions(-) diff --git a/config/config.exs b/config/config.exs index fb04c85..946c37f 100644 --- a/config/config.exs +++ b/config/config.exs @@ -1,30 +1,3 @@ -# This file is responsible for configuring your application -# and its dependencies with the aid of the Mix.Config module. use Mix.Config -# This configuration is loaded before any dependency and is restricted -# to this project. If another project depends on this project, this -# file won't be loaded nor affect the parent project. For this reason, -# if you want to provide default values for your application for -# third-party users, it should be done in your "mix.exs" file. - -# You can configure your application as: -# -# config :dsl, key: :value -# -# and access this configuration in your application as: -# -# Application.get_env(:dsl, :key) -# -# You can also configure a third-party app: -# -# config :logger, level: :info -# - -# It is also possible to import configuration files, relative to this -# directory. For example, you can emulate configuration per environment -# by uncommenting the line below and defining dev.exs, test.exs and such. -# Configuration from the imported file will override the ones defined -# here (which is why it is important to import them last). -# -# import_config "#{Mix.env()}.exs" +config :tesla, adapter: Tesla.Adapter.Hackney