Relay: Fix hasFragmentData for Non-Deferred Fragments

Reviewed By: josephsavona Differential Revision: D3096558 fb-gh-sync-id: e809a93ca895896f8654146a94352b76ffd523c3 shipit-source-id: e809a93ca895896f8654146a94352b76ffd523c3
facebook · Mar 25, 2016 · 97c977a · 97c977a
1 parent f23a4b4
commit 97c977a
Showing 1 changed file with 10 additions and 0 deletions.
diff --git a/src/container/RelayContainer.js b/src/container/RelayContainer.js
@@ -369,6 +369,16 @@ function createContainerComponent(
       fragmentReference: RelayFragmentReference,
       record: Object
     ): boolean {
+      if (!fragmentReference.isDeferred()) {
+        warning(
+          false,
+          'RelayContainer.hasFragmentData(): Method should only be called ' +
+          'with deferred fragments. However, `%s` is calling it with a ' +
+          'fragment that is not deferred.',
+          componentName
+        );
+        return true;
+      }
       // convert builder -> fragment in order to get the fragment's name
       const dataID = RelayRecord.getDataIDForObject(record);
       invariant(