relay-compiler 18.0.0 → 18.2.0

Sign up to get free protection for your applications and to get access to all the features.
@@ -137,6 +137,7 @@ directive @connection(
137
137
  filters: [String]
138
138
  handler: String
139
139
  dynamicKey_UNSTABLE: String
140
+ prefetchable_pagination: Boolean = false
140
141
  ) on FIELD
141
142
 
142
143
  directive @stream_connection(
@@ -148,6 +149,7 @@ directive @stream_connection(
148
149
  if: Boolean = true
149
150
  use_customized_batch: Boolean = false
150
151
  dynamicKey_UNSTABLE: String
152
+ prefetchable_pagination: Boolean = false
151
153
  ) on FIELD
152
154
 
153
155
  # RequiredTransform
@@ -183,10 +185,15 @@ directive @required(action: RequiredFieldAction! @static) on FIELD
183
185
  """
184
186
  (Relay Only)
185
187
 
186
- `@catch` is a directive you can add to fields in your Relay queries to
187
- declare how errors are handled.
188
+ `@catch` is a directive you can add to fields, fragment definitions, queries,
189
+ mutations, and aliased inline fragments to opt into explicitly handling field
190
+ errors.
191
+
192
+ [Read More](https://relay.dev/docs/guides/catch-directive/)
188
193
  """
189
- directive @catch(to: CatchFieldTo! = RESULT @static) on FIELD
194
+ directive @catch(
195
+ to: CatchFieldTo! = RESULT @static
196
+ ) on FIELD | FRAGMENT_DEFINITION | QUERY | MUTATION | INLINE_FRAGMENT
190
197
 
191
198
  # DeclarativeConnection
192
199
  """
@@ -318,9 +325,17 @@ directive @alias(as: String) on FRAGMENT_SPREAD | INLINE_FRAGMENT
318
325
  """
319
326
  (Relay Only)
320
327
 
321
- This directive allows users to opt out of validation which enforces that @alias
322
- be used on all fragment spreads which might not match. It is intended as an
323
- escape hatch for incremental adoption of enforcing `@alias`.
328
+ **To resolve, replace `@dangerously_unaliased_fixme` with `@alias`**
329
+
330
+ This fragment spread will only conditionally be fetched, either due to
331
+ `@skip`/@include` or its type condition. Conditionally fetched fragments without
332
+ an `@alias` are unsafe because they don't expose any mechanism for the user to
333
+ check if the data was fetched before using the fragment. In these cases `@alias`
334
+ will materialize the fragment as a nullable named property, ensuring the proper
335
+ null checks are performed.
336
+
337
+ We now require all such fragment spreads to use `@alias`, and have marked
338
+ existing unsafe spreads with `@dangerously_unaliased_fixme`.
324
339
 
325
340
  DO NOT ADD NEW USES OF THIS DIRECTIVE.
326
341
 
@@ -337,3 +352,19 @@ If a non-static value is provided, it will result in a validation error.
337
352
  Used for arguments which are expected to be read by the Relay compiler.
338
353
  """
339
354
  directive @static on ARGUMENT_DEFINITION
355
+
356
+ """
357
+ (Relay Only)
358
+
359
+ Used for printing a query, need to be used with `debug_transform`
360
+ """
361
+ directive @__debug on QUERY | MUTATION | SUBSCRIPTION | FRAGMENT_DEFINITION
362
+
363
+ """
364
+ (Relay Only)
365
+
366
+ If added to a query, resolvers in that query to run at exec-time, rather than read-time.
367
+ This means the resolvers are run when the query data is requested rather than when the
368
+ query is used (i.e. when the network request is made instead of at render time).
369
+ """
370
+ directive @exec_time_resolvers on QUERY
package/win-x64/relay.exe CHANGED
Binary file