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
Copy file name to clipboardExpand all lines: docs/dyn/firebasedataconnect_v1.projects.locations.services.connectors.html
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -243,7 +243,10 @@ <h3>Method Details</h3>
243
243
"errors": [ # Errors of this response.
244
244
{ # GraphqlError conforms to the GraphQL error spec. https://spec.graphql.org/draft/#sec-Errors Firebase Data Connect API surfaces `GraphqlError` in various APIs: - Upon compile error, `UpdateSchema` and `UpdateConnector` return Code.Invalid_Argument with a list of `GraphqlError` in error details. - Upon query compile error, `ExecuteGraphql` and `ExecuteGraphqlRead` return Code.OK with a list of `GraphqlError` in response body. - Upon query execution error, `ExecuteGraphql`, `ExecuteGraphqlRead`, `ExecuteMutation` and `ExecuteQuery` all return Code.OK with a list of `GraphqlError` in response body.
245
245
"extensions": { # GraphqlErrorExtensions contains additional information of `GraphqlError`. # Additional error information.
246
+
"code": "A String", # Maps to canonical gRPC codes. If not specified, it represents `Code.INTERNAL`.
247
+
"debugDetails": "A String", # More detailed error message to assist debugging. In the backend, only include it in admin authenticated API like ExecuteGraphql. In the emulator, always include it to assist debugging.
246
248
"file": "A String", # The source file name where the error occurred. Included only for `UpdateSchema` and `UpdateConnector`, it corresponds to `File.path` of the provided `Source`.
249
+
"resource": "A String", # Distinguish which schema or connector the error originates from. It should be set on errors from control plane APIs (e.g. `UpdateSchema`, `UpdateConnector`).
247
250
},
248
251
"locations": [ # The source locations where the error occurred. Locations should help developers and toolings identify the source of error quickly. Included in admin endpoints (`ExecuteGraphql`, `ExecuteGraphqlRead`, `UpdateSchema` and `UpdateConnector`) to reference the provided GraphQL GQL document. Omitted in `ExecuteMutation` and `ExecuteQuery` since the caller shouldn't have access access the underlying GQL source.
249
252
{ # SourceLocation references a location in a GraphQL source.
@@ -291,7 +294,10 @@ <h3>Method Details</h3>
291
294
"errors": [ # Errors of this response.
292
295
{ # GraphqlError conforms to the GraphQL error spec. https://spec.graphql.org/draft/#sec-Errors Firebase Data Connect API surfaces `GraphqlError` in various APIs: - Upon compile error, `UpdateSchema` and `UpdateConnector` return Code.Invalid_Argument with a list of `GraphqlError` in error details. - Upon query compile error, `ExecuteGraphql` and `ExecuteGraphqlRead` return Code.OK with a list of `GraphqlError` in response body. - Upon query execution error, `ExecuteGraphql`, `ExecuteGraphqlRead`, `ExecuteMutation` and `ExecuteQuery` all return Code.OK with a list of `GraphqlError` in response body.
293
296
"extensions": { # GraphqlErrorExtensions contains additional information of `GraphqlError`. # Additional error information.
297
+
"code": "A String", # Maps to canonical gRPC codes. If not specified, it represents `Code.INTERNAL`.
298
+
"debugDetails": "A String", # More detailed error message to assist debugging. In the backend, only include it in admin authenticated API like ExecuteGraphql. In the emulator, always include it to assist debugging.
294
299
"file": "A String", # The source file name where the error occurred. Included only for `UpdateSchema` and `UpdateConnector`, it corresponds to `File.path` of the provided `Source`.
300
+
"resource": "A String", # Distinguish which schema or connector the error originates from. It should be set on errors from control plane APIs (e.g. `UpdateSchema`, `UpdateConnector`).
295
301
},
296
302
"locations": [ # The source locations where the error occurred. Locations should help developers and toolings identify the source of error quickly. Included in admin endpoints (`ExecuteGraphql`, `ExecuteGraphqlRead`, `UpdateSchema` and `UpdateConnector`) to reference the provided GraphQL GQL document. Omitted in `ExecuteMutation` and `ExecuteQuery` since the caller shouldn't have access access the underlying GQL source.
297
303
{ # SourceLocation references a location in a GraphQL source.
Copy file name to clipboardExpand all lines: docs/dyn/firebasedataconnect_v1.projects.locations.services.html
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -254,7 +254,10 @@ <h3>Method Details</h3>
254
254
"errors": [ # Errors of this response. If the data entry in the response is not present, the errors entry must be present. It conforms to https://spec.graphql.org/draft/#sec-Errors.
255
255
{ # GraphqlError conforms to the GraphQL error spec. https://spec.graphql.org/draft/#sec-Errors Firebase Data Connect API surfaces `GraphqlError` in various APIs: - Upon compile error, `UpdateSchema` and `UpdateConnector` return Code.Invalid_Argument with a list of `GraphqlError` in error details. - Upon query compile error, `ExecuteGraphql` and `ExecuteGraphqlRead` return Code.OK with a list of `GraphqlError` in response body. - Upon query execution error, `ExecuteGraphql`, `ExecuteGraphqlRead`, `ExecuteMutation` and `ExecuteQuery` all return Code.OK with a list of `GraphqlError` in response body.
256
256
"extensions": { # GraphqlErrorExtensions contains additional information of `GraphqlError`. # Additional error information.
257
+
"code": "A String", # Maps to canonical gRPC codes. If not specified, it represents `Code.INTERNAL`.
258
+
"debugDetails": "A String", # More detailed error message to assist debugging. In the backend, only include it in admin authenticated API like ExecuteGraphql. In the emulator, always include it to assist debugging.
257
259
"file": "A String", # The source file name where the error occurred. Included only for `UpdateSchema` and `UpdateConnector`, it corresponds to `File.path` of the provided `Source`.
260
+
"resource": "A String", # Distinguish which schema or connector the error originates from. It should be set on errors from control plane APIs (e.g. `UpdateSchema`, `UpdateConnector`).
258
261
},
259
262
"locations": [ # The source locations where the error occurred. Locations should help developers and toolings identify the source of error quickly. Included in admin endpoints (`ExecuteGraphql`, `ExecuteGraphqlRead`, `UpdateSchema` and `UpdateConnector`) to reference the provided GraphQL GQL document. Omitted in `ExecuteMutation` and `ExecuteQuery` since the caller shouldn't have access access the underlying GQL source.
260
263
{ # SourceLocation references a location in a GraphQL source.
@@ -311,7 +314,10 @@ <h3>Method Details</h3>
311
314
"errors": [ # Errors of this response. If the data entry in the response is not present, the errors entry must be present. It conforms to https://spec.graphql.org/draft/#sec-Errors.
312
315
{ # GraphqlError conforms to the GraphQL error spec. https://spec.graphql.org/draft/#sec-Errors Firebase Data Connect API surfaces `GraphqlError` in various APIs: - Upon compile error, `UpdateSchema` and `UpdateConnector` return Code.Invalid_Argument with a list of `GraphqlError` in error details. - Upon query compile error, `ExecuteGraphql` and `ExecuteGraphqlRead` return Code.OK with a list of `GraphqlError` in response body. - Upon query execution error, `ExecuteGraphql`, `ExecuteGraphqlRead`, `ExecuteMutation` and `ExecuteQuery` all return Code.OK with a list of `GraphqlError` in response body.
313
316
"extensions": { # GraphqlErrorExtensions contains additional information of `GraphqlError`. # Additional error information.
317
+
"code": "A String", # Maps to canonical gRPC codes. If not specified, it represents `Code.INTERNAL`.
318
+
"debugDetails": "A String", # More detailed error message to assist debugging. In the backend, only include it in admin authenticated API like ExecuteGraphql. In the emulator, always include it to assist debugging.
314
319
"file": "A String", # The source file name where the error occurred. Included only for `UpdateSchema` and `UpdateConnector`, it corresponds to `File.path` of the provided `Source`.
320
+
"resource": "A String", # Distinguish which schema or connector the error originates from. It should be set on errors from control plane APIs (e.g. `UpdateSchema`, `UpdateConnector`).
315
321
},
316
322
"locations": [ # The source locations where the error occurred. Locations should help developers and toolings identify the source of error quickly. Included in admin endpoints (`ExecuteGraphql`, `ExecuteGraphqlRead`, `UpdateSchema` and `UpdateConnector`) to reference the provided GraphQL GQL document. Omitted in `ExecuteMutation` and `ExecuteQuery` since the caller shouldn't have access access the underlying GQL source.
317
323
{ # SourceLocation references a location in a GraphQL source.
Copy file name to clipboardExpand all lines: docs/dyn/firebasedataconnect_v1beta.projects.locations.services.connectors.html
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -243,7 +243,10 @@ <h3>Method Details</h3>
243
243
"errors": [ # Errors of this response.
244
244
{ # GraphqlError conforms to the GraphQL error spec. https://spec.graphql.org/draft/#sec-Errors Firebase Data Connect API surfaces `GraphqlError` in various APIs: - Upon compile error, `UpdateSchema` and `UpdateConnector` return Code.Invalid_Argument with a list of `GraphqlError` in error details. - Upon query compile error, `ExecuteGraphql` and `ExecuteGraphqlRead` return Code.OK with a list of `GraphqlError` in response body. - Upon query execution error, `ExecuteGraphql`, `ExecuteGraphqlRead`, `ExecuteMutation` and `ExecuteQuery` all return Code.OK with a list of `GraphqlError` in response body.
245
245
"extensions": { # GraphqlErrorExtensions contains additional information of `GraphqlError`. # Additional error information.
246
+
"code": "A String", # Maps to canonical gRPC codes. If not specified, it represents `Code.INTERNAL`.
247
+
"debugDetails": "A String", # More detailed error message to assist debugging. In the backend, only include it in admin authenticated API like ExecuteGraphql. In the emulator, always include it to assist debugging.
246
248
"file": "A String", # The source file name where the error occurred. Included only for `UpdateSchema` and `UpdateConnector`, it corresponds to `File.path` of the provided `Source`.
249
+
"resource": "A String", # Distinguish which schema or connector the error originates from. It should be set on errors from control plane APIs (e.g. `UpdateSchema`, `UpdateConnector`).
247
250
},
248
251
"locations": [ # The source locations where the error occurred. Locations should help developers and toolings identify the source of error quickly. Included in admin endpoints (`ExecuteGraphql`, `ExecuteGraphqlRead`, `UpdateSchema` and `UpdateConnector`) to reference the provided GraphQL GQL document. Omitted in `ExecuteMutation` and `ExecuteQuery` since the caller shouldn't have access access the underlying GQL source.
249
252
{ # SourceLocation references a location in a GraphQL source.
@@ -291,7 +294,10 @@ <h3>Method Details</h3>
291
294
"errors": [ # Errors of this response.
292
295
{ # GraphqlError conforms to the GraphQL error spec. https://spec.graphql.org/draft/#sec-Errors Firebase Data Connect API surfaces `GraphqlError` in various APIs: - Upon compile error, `UpdateSchema` and `UpdateConnector` return Code.Invalid_Argument with a list of `GraphqlError` in error details. - Upon query compile error, `ExecuteGraphql` and `ExecuteGraphqlRead` return Code.OK with a list of `GraphqlError` in response body. - Upon query execution error, `ExecuteGraphql`, `ExecuteGraphqlRead`, `ExecuteMutation` and `ExecuteQuery` all return Code.OK with a list of `GraphqlError` in response body.
293
296
"extensions": { # GraphqlErrorExtensions contains additional information of `GraphqlError`. # Additional error information.
297
+
"code": "A String", # Maps to canonical gRPC codes. If not specified, it represents `Code.INTERNAL`.
298
+
"debugDetails": "A String", # More detailed error message to assist debugging. In the backend, only include it in admin authenticated API like ExecuteGraphql. In the emulator, always include it to assist debugging.
294
299
"file": "A String", # The source file name where the error occurred. Included only for `UpdateSchema` and `UpdateConnector`, it corresponds to `File.path` of the provided `Source`.
300
+
"resource": "A String", # Distinguish which schema or connector the error originates from. It should be set on errors from control plane APIs (e.g. `UpdateSchema`, `UpdateConnector`).
295
301
},
296
302
"locations": [ # The source locations where the error occurred. Locations should help developers and toolings identify the source of error quickly. Included in admin endpoints (`ExecuteGraphql`, `ExecuteGraphqlRead`, `UpdateSchema` and `UpdateConnector`) to reference the provided GraphQL GQL document. Omitted in `ExecuteMutation` and `ExecuteQuery` since the caller shouldn't have access access the underlying GQL source.
297
303
{ # SourceLocation references a location in a GraphQL source.
Copy file name to clipboardExpand all lines: docs/dyn/firebasedataconnect_v1beta.projects.locations.services.html
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -254,7 +254,10 @@ <h3>Method Details</h3>
254
254
"errors": [ # Errors of this response. If the data entry in the response is not present, the errors entry must be present. It conforms to https://spec.graphql.org/draft/#sec-Errors.
255
255
{ # GraphqlError conforms to the GraphQL error spec. https://spec.graphql.org/draft/#sec-Errors Firebase Data Connect API surfaces `GraphqlError` in various APIs: - Upon compile error, `UpdateSchema` and `UpdateConnector` return Code.Invalid_Argument with a list of `GraphqlError` in error details. - Upon query compile error, `ExecuteGraphql` and `ExecuteGraphqlRead` return Code.OK with a list of `GraphqlError` in response body. - Upon query execution error, `ExecuteGraphql`, `ExecuteGraphqlRead`, `ExecuteMutation` and `ExecuteQuery` all return Code.OK with a list of `GraphqlError` in response body.
256
256
"extensions": { # GraphqlErrorExtensions contains additional information of `GraphqlError`. # Additional error information.
257
+
"code": "A String", # Maps to canonical gRPC codes. If not specified, it represents `Code.INTERNAL`.
258
+
"debugDetails": "A String", # More detailed error message to assist debugging. In the backend, only include it in admin authenticated API like ExecuteGraphql. In the emulator, always include it to assist debugging.
257
259
"file": "A String", # The source file name where the error occurred. Included only for `UpdateSchema` and `UpdateConnector`, it corresponds to `File.path` of the provided `Source`.
260
+
"resource": "A String", # Distinguish which schema or connector the error originates from. It should be set on errors from control plane APIs (e.g. `UpdateSchema`, `UpdateConnector`).
258
261
},
259
262
"locations": [ # The source locations where the error occurred. Locations should help developers and toolings identify the source of error quickly. Included in admin endpoints (`ExecuteGraphql`, `ExecuteGraphqlRead`, `UpdateSchema` and `UpdateConnector`) to reference the provided GraphQL GQL document. Omitted in `ExecuteMutation` and `ExecuteQuery` since the caller shouldn't have access access the underlying GQL source.
260
263
{ # SourceLocation references a location in a GraphQL source.
@@ -311,7 +314,10 @@ <h3>Method Details</h3>
311
314
"errors": [ # Errors of this response. If the data entry in the response is not present, the errors entry must be present. It conforms to https://spec.graphql.org/draft/#sec-Errors.
312
315
{ # GraphqlError conforms to the GraphQL error spec. https://spec.graphql.org/draft/#sec-Errors Firebase Data Connect API surfaces `GraphqlError` in various APIs: - Upon compile error, `UpdateSchema` and `UpdateConnector` return Code.Invalid_Argument with a list of `GraphqlError` in error details. - Upon query compile error, `ExecuteGraphql` and `ExecuteGraphqlRead` return Code.OK with a list of `GraphqlError` in response body. - Upon query execution error, `ExecuteGraphql`, `ExecuteGraphqlRead`, `ExecuteMutation` and `ExecuteQuery` all return Code.OK with a list of `GraphqlError` in response body.
313
316
"extensions": { # GraphqlErrorExtensions contains additional information of `GraphqlError`. # Additional error information.
317
+
"code": "A String", # Maps to canonical gRPC codes. If not specified, it represents `Code.INTERNAL`.
318
+
"debugDetails": "A String", # More detailed error message to assist debugging. In the backend, only include it in admin authenticated API like ExecuteGraphql. In the emulator, always include it to assist debugging.
314
319
"file": "A String", # The source file name where the error occurred. Included only for `UpdateSchema` and `UpdateConnector`, it corresponds to `File.path` of the provided `Source`.
320
+
"resource": "A String", # Distinguish which schema or connector the error originates from. It should be set on errors from control plane APIs (e.g. `UpdateSchema`, `UpdateConnector`).
315
321
},
316
322
"locations": [ # The source locations where the error occurred. Locations should help developers and toolings identify the source of error quickly. Included in admin endpoints (`ExecuteGraphql`, `ExecuteGraphqlRead`, `UpdateSchema` and `UpdateConnector`) to reference the provided GraphQL GQL document. Omitted in `ExecuteMutation` and `ExecuteQuery` since the caller shouldn't have access access the underlying GQL source.
317
323
{ # SourceLocation references a location in a GraphQL source.
0 commit comments