-
Notifications
You must be signed in to change notification settings - Fork 40
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Hi, first off thanks for this great lib! I've been using it for quite a while now and really love the improvements over the stock formatter.
Issue
Styler 1.0.0's extensive reformatting of config files separates many code comments from the lines they're annotating.
Versions
- Elixir:
Erlang/OTP 27 [erts-15.0] [source] [64-bit] [smp:10:10] [ds:10:10:10] [async-threads:1] [jit]
Elixir 1.17.1 (compiled with Erlang/OTP 25)
- Styler:
locked at 1.0.0 (styler) 4ba5bc40
Example Input
import Config
# Only in tests, remove the complexity from the password hashing algorithm
config :bcrypt_elixir, :log_rounds, 1
# We don't run a server during test. If one is required,
# you can enable the server option below.
config :ido, IdoWeb.Endpoint,
http: [port: 4001],
server: false
config :ido,
env: :test
config :ex_aws,
access_key_id: "bogus",
secret_access_key: "also bogus"
# Print only error messages during test
config :logger, level: :error
# Make bcrypt fast (and unsafe) for testing only
config :bcrypt_elixir, log_rounds: 4
# Configure your database
config :ido, Ido.Repo,
adapter: Ecto.Adapters.Postgres,
types: Ido.PostgrexTypes,
username: "postgres",
password: "postgres",
database: "ido_test",
hostname: "localhost",
pool: Ecto.Adapters.SQL.Sandbox
# Env variables
config :ido,
photo_api: Ido.PhotoApiMock,
email_parser: Ido.EmailParserMock,
geocoding_api: Ido.GeocodingApiMock,
photo_cdn: Ido.PhotoCDNMock,
google_maps: Ido.GoogleMapsMock,
sendgrid_inbound_key: "FAKE_API_KEY"
config :ido, Oban, testing: :inline
# increase login attempts to not interfere with tests
config :ido, max_login_attempts: 500
config :appsignal, :config, active: falseStacktrace / Current Behaviour
import Config
config :appsignal, :config, active: false
# Only in tests, remove the complexity from the password hashing algorithm
config :bcrypt_elixir, :log_rounds, 1
# Make bcrypt fast (and unsafe) for testing only
config :bcrypt_elixir, log_rounds: 4
config :ex_aws,
access_key_id: "bogus",
secret_access_key: "also bogus"
# Configure your database
config :ido, Ido.Repo,
adapter: Ecto.Adapters.Postgres,
types: Ido.PostgrexTypes,
username: "postgres",
password: "postgres",
database: "ido_test",
hostname: "localhost",
# We don't run a server during test. If one is required,
# you can enable the server option below.
pool: Ecto.Adapters.SQL.Sandbox
config :ido, IdoWeb.Endpoint,
http: [port: 4001],
server: false
config :ido, Oban, testing: :inline
config :ido,
env: :test
# increase login attempts to not interfere with tests
# Env variables
config :ido, max_login_attempts: 500
config :ido,
photo_api: Ido.PhotoApiMock,
email_parser: Ido.EmailParserMock,
geocoding_api: Ido.GeocodingApiMock,
photo_cdn: Ido.PhotoCDNMock,
google_maps: Ido.GoogleMapsMock,
sendgrid_inbound_key: "FAKE_API_KEY"
# Print only error messages during test
config :logger, level: :errorNotice several blocks of code have been separated from their respective comments:
# Env variables# We don't run a server during test. If one is required,
In my more complex config files (prod, runtime, dev), it's even messier.
Is there a different style of code commenting I should be using to prevent this? The majority of my config comments are scaffolded from the generators, so I won't be alone in hitting this.
jakepremKitton
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working