Skip to content

Remove lager parse transform #140

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 9, 2015
Merged

Remove lager parse transform #140

merged 1 commit into from
Jul 9, 2015

Conversation

ahf
Copy link
Contributor

@ahf ahf commented Jun 14, 2015

Whilst debugging something where I disabled the cuttlefish dependency, I noticed that lager applied the lager parse transform without actually using lager anywhere. This patch removes the lager_transform from erl_opts.

@jonmeredith
Copy link
Contributor

Is this a code hygiene issue for you, or were you trying to use eleveldb in a project without lager?
(seems unlikely given the eleveldb -> cfish -> lager dep chain)

@ahf
Copy link
Contributor Author

ahf commented Jun 15, 2015

I'm not sure I'd use the term code hygiene here.

It's unclean to have a parse transform applied from something that isn't an explicit dependency IMO, and yes, I'm using eleveldb in an environment where we are not using cuttlefish and thus doesn't fetch the implicit lager dependency (which works just fine as well). There's no calls to lager:* inside of eleveldb itself.

@tsloughter
Copy link

Yea, it is just not right, so why keep it?

@jonmeredith
Copy link
Contributor

Agreed.

jonmeredith pushed a commit that referenced this pull request Jul 9, 2015
Remove lager parse transform
@jonmeredith jonmeredith merged commit e389149 into basho:develop Jul 9, 2015
jonmeredith pushed a commit that referenced this pull request Jul 9, 2015
Remove lager parse transform
jonmeredith pushed a commit that referenced this pull request Jul 9, 2015
Remove lager parse transform
@jonmeredith
Copy link
Contributor

Applied to 2.0 and 2.1 branches too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants