Execution without elvis.config shows no issues about elvis_core HOT 6 CLOSED

Should this be kept open? Is it something we want to take care of? We'd remove the need to sync. changes in the defaults, for example, from elvis to rebar3_lint.

from elvis_core.

I think that elvis_core should be the place to keep the defaults, but I'm not sure this is a pressing issue right now. However, I don't have enough data to know how many people uses elvis as a standalone script vs. how many people uses elvis_core through rebar_lint.

from elvis_core.

I used to use elvis as a standalone script until I found out about the plugin. In any case, if there's defaults in elvis_core (for an empty/non-existing elvis.config) this means that rebar3_lint has only to import a new version, at every release (well, until @Licenser decides to implement specific options, that is 😄).

from elvis_core.

I'm not actively changing rebar3_lint but I'm more then happy to merge any PR that improves it's behavior :)

from elvis_core.

Is this solved already, @paulo-ferraz-oliveira ?

from elvis_core.

Two things:

1. I'm not actively using the CLI elvis anymore, but assume the issue hasn't been fixed (I saw nothing in my notifications that pointed to it),
2. I still would like rebar3_lint to not assume any defaults (and leave that to elvis_core), but that's an issue for a different repo (I went to check it, and you've solved it already, hurrah!).

I think it's safe to close.

from elvis_core.