Skip to content
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

Rename level to tree_level #60

Merged
merged 4 commits into from
Jan 18, 2017

Conversation

markhgbrewster
Copy link

I have had a go at trying to fix the issue around the level described here: #58.

I am not sure if it is something you would want to add in but It does seem to solve the problem if replicate the scenario locally.

I have renamed the level method tree_level as suggested. I also think I have been able to allow level to to be used if level is not a column on the recode concerned. I have written some tests to cover such a scenario and tested manually in a rails app and it seem to work ok. Let me know what you think.

Also I spotted some typos in my previous work I have correct these and in the first commit so they can be cherry picked if the rest of the work is not wanted.

@felixbuenemann
Copy link
Collaborator

felixbuenemann commented Jan 12, 2017

Looks good to me, I'll look into fixing the test failures on master due to the ruby version requirement of nokogiri 1.7.

@felixbuenemann felixbuenemann changed the title Rename level tree_level Rename level to tree_level Jan 12, 2017
@markhgbrewster
Copy link
Author

Thanks

@felixbuenemann felixbuenemann merged commit 622f52b into amerine:master Jan 18, 2017
@felixbuenemann
Copy link
Collaborator

Merged your changes, thanks for taking the time to look into this.

I'll release gem version 2.6.1 with this fix shortly.

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.

2 participants