You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Passing preexisting query-payload pairs to prepareData() is messy when the query contains aliased parameterized fields, because Relay modifies the field names to prevent name collisions. To make a preexisting query-response pair for a query containing aliased parameterized fields, I need to use a Relay internal function generateRQLFieldAlias() to produce a valid response. This what I’m doing:
Related to #50
Passing preexisting query-payload pairs to prepareData() is messy when the query contains aliased parameterized fields, because Relay modifies the field names to prevent name collisions. To make a preexisting query-response pair for a query containing aliased parameterized fields, I need to use a Relay internal function
generateRQLFieldAlias()
to produce a valid response. This what I’m doing:Example query:
Function to generate response for query-response pair:
Does it seem reasonable to submit a pull request to Relay to make a public interface to the
generatedRQLFieldAlias()
function for this purpose?The text was updated successfully, but these errors were encountered: