-
Notifications
You must be signed in to change notification settings - Fork 52
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
Type errors when defining fragments using @ppxCustom #207
Comments
Possibly this is a bug indeed (perhaps particularly with a top level The recursive modules where one of the last features that were added to the 1.0 release. Thanks for stress testing them! |
I'd be happy to add the failing query and seeing about fixing it also. Let me get get the build and tests working first (as per my questions in #205) |
@jfrolich Just following up on this since it's blocking our migration from the old ppx. I have a branch with a non-compiling test. (I didn't write a proper test since that's hard to do with a query that doesn't compile, the branch is mainly for illustrative purposes.) Could you please look into fixing it? |
Yes will look at this ASAP! |
I've been trying to use
@ppxCustom
on this fragmentwhere
User
has the following definitionThe recursive version
fails with
I also tried the less compact non-recursive version which fails with the same error (naming is slightly different but that is immaterial).
A very similar approach works with a query
currentUser: User
The text was updated successfully, but these errors were encountered: