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

Try to fix 1.9-dev branch #1849

Merged
merged 13 commits into from
Sep 13, 2018
Merged

Try to fix 1.9-dev branch #1849

merged 13 commits into from
Sep 13, 2018

Conversation

rmosolgo
Copy link
Owner

A while ago, I was trying to get master changes into 1.9-dev, and somehow, I broke it. It had something to do with field extensions, and how it was reverted on master.

So I just now made a new branch from master, cherry-picked all the merge commits from https://github.com/rmosolgo/graphql-ruby/milestone/67?closed=1, and now I think I can merge that into 1.9-dev and maybe we'll be in good shape.

modosc and others added 13 commits August 16, 2018 09:45
Previously this used `instance_exec` which sets `self` to the field
instance.

This changes to `yield` which still yields the field instance
(supporting the same functionality) but doesn't change `self`.
add GraphQL::Types::ISO8601DateTime.time_precision to customize time pricisions
support callable prepare objects in Schema::Argument (fixes #1786)
…yielding

Update how Schema::Field executes definition_block
[Language::Visitor] use method-based visit handlers
Don't pass resolver objects to field extensions
Change the default behavior of the encoder to use `urlsafe` versions
@rmosolgo rmosolgo added this to the 1.9.0 milestone Sep 13, 2018
@rmosolgo rmosolgo merged commit 52ddbbf into 1.9-dev Sep 13, 2018
@rmosolgo rmosolgo deleted the 1.9-dev-2 branch October 5, 2018 19:52
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.

6 participants