-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Docs need to mention null
usage for initialVariables
#700
Comments
RavenHursT
pushed a commit
to RavenHursT/relay
that referenced
this issue
Dec 22, 2015
@RavenHursT This is technically true, but I'm curious: why are you managing the |
@devknoll : Server-side rendering.. if I go to |
venepe
pushed a commit
to venepe/relay
that referenced
this issue
Mar 7, 2016
Summary:Added information in Container API docs for null usage in initialVariables. Fixes facebook#700 Closes facebook#701 Differential Revision: D3001979 Pulled By: yungsters fb-gh-sync-id: ceaf7e4cf0f45ed4f354a041b6ab474b66d23eff shipit-source-id: ceaf7e4cf0f45ed4f354a041b6ab474b66d23eff
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The docs for setting
initialVariables
for the Container API do not mention how to initialize unknown values for variables (i.e. The initialcursor
value for pagination).The correct way to initialize variables w/ an unknown value is to use
null
. It took over half a day of searching and asking before this answer was given to me:http://stackoverflow.com/questions/34406667/relay-pagination-how-to-initialize-after-value/34407181#34407181
This should definitely be in the documentation for this feature.
The text was updated successfully, but these errors were encountered: