bitwalker / bitwalker/conform

An issue with conform.new

Open
#157 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Elixir
Stars
378
Forks
59
PR merge metrics
No merged PRs in 30d

Description

I have config like this in config/config.exs:

`config :logger, backends: [{ Airbrake.LoggerBackend, :error }, :console]`

when I run

`mix conform.new`

I get the following

```
[
extends: [],
import: [],
mappings: [
"logger.backends": [
commented: false,
datatype: [
list: [
{:atom, :atom},
:atom
]
],
default: [
{:"Airbrake.LoggerBackend", :error},
:console
],
doc: "Provide documentation for logger.backends here.",
hidden: false,
to: "logger.backends"
]
],
transforms: [],
validators: []
]
```

on startup this results in sys.config having this entry:
```
{logger,
[{backends,[{'Airbrake.LoggerBackend',error},console]}]}
```

which is obviously incorrect. It has to be 'Elixir.Airbrake.LoggerBackend'. So on startup this fails.

has anyone seen this problem? Is there a solution?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.