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

Live resolvers: return value when throw #4876

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pavelglac
Copy link

@pavelglac pavelglac commented Jan 9, 2025

Following the issue #4877

This PR aims to return null instead of undefined for live resolvers when the resolver throws an error. That is based on docs

@facebook-github-bot
Copy link
Contributor

Hi @pavelglac!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@captbaritone
Copy link
Contributor

Looks like this is specifically covering the case where a live resolver reads a fragment which is missing data?

Just clarifying since I think it's worth considering if we want to treat that as equivalent to "an individual resolver throws an error". I'm not saying they shouldn't be treated as equivalent, but I think it merits contemplating the implications.

@pavelglac
Copy link
Author

@captbaritone This is the case when resolver does not return LiveState at all. If resolver throws in read that is different case. In this case the result is null for resolver but the value is not saved. In version 17 it was handled by ResolverCache.js which was saving value from result.

/**
 * @RelayResolver Query.counter: Int
 * @live
 */
export function counter(){
  throw new Error("Error");

  return {
    read: ...
    subscribe: ...,
  };
}

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

Successfully merging this pull request may close these issues.

3 participants