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

Rails 6.1 Compatability #32

Merged
merged 4 commits into from
May 26, 2021
Merged

Rails 6.1 Compatability #32

merged 4 commits into from
May 26, 2021

Conversation

walski
Copy link
Contributor

@walski walski commented Nov 23, 2020

This allows working with Rails 6.1 RC1.

Thorben Starsy added 4 commits November 24, 2020 00:04
The DepthFirst visitor got removed from Arel [0]. This inlines a very
simple depth first traversal to cover the needs of the join condition
column "listing" without relying on the removed DepthFirst visitor.

[0] https://github.com/rails/rails/pull/36492/files
@walski walski mentioned this pull request Nov 23, 2020
@walski
Copy link
Contributor Author

walski commented Dec 4, 2020

We're using this in production, now.

@shellixyz
Copy link

shellixyz commented Jan 30, 2021

I can confirm this PR is working fine for me with Rails 6.1. Thanks @walski

@sposin
Copy link

sposin commented Feb 25, 2021

Is there a particular reason this hasn't been merged?

@travisofthenorth
Copy link

@zachaysan you mind taking a look at this? Blocking 6.1 upgrade for us.

@zachaysan
Copy link
Collaborator

@travisofthenorth, @walski and everyone else: I'm very sorry, I was hospitalized and in otherwise poor health for months and this slipped. I'll merge and cut a gem for this now. Thank you very much for bringing it to my attention.

@zachaysan zachaysan merged commit 6e8eab1 into take-five:master May 26, 2021
@zachaysan
Copy link
Collaborator

@travisofthenorth I've pushed the gem to rubygems, let me know if you have any trouble.

https://rubygems.org/gems/activerecord-hierarchical_query/versions/1.3.0

@travisofthenorth
Copy link

@zachaysan no worries. Thank you so much for the quick turnaround!

@zachaysan
Copy link
Collaborator

@travisofthenorth it's the least I could do.

I should investigate getting another maintainer in the event that this happens again, as my medical condition, while fine for now, could reappear. If you or @walski have any interest let me know.

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.

None yet

5 participants