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

Write test for nulled fragment data #3

Open
rexxars opened this issue Aug 4, 2015 · 0 comments
Open

Write test for nulled fragment data #3

rexxars opened this issue Aug 4, 2015 · 0 comments

Comments

@rexxars
Copy link
Contributor

rexxars commented Aug 4, 2015

I'm having a hard time figuring out the flow and how this bug occurs. Basically it has to do with references that can't be resolved (0, for instance). They are returned from the fetcher as null and something in the resolve-fragment code tries to map over the values and extract the IDs from it. That obviously fails when encountering a null.

I hotfixed it with d566b43, but someone(tm) should add a test to ensure there are no regressions later.

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

No branches or pull requests

1 participant