mirror of
https://github.com/firebase/firebase-ios-sdk
synced 2026-11-10 22:45:59 +05:45
* Rename nanopb/.../*.pb.c to nanopb/.../*.nanopb.c This ensures that all generated nanopb files use the same (sub) extension of nanopb. This matches up with nanopb's --extension parameter (which will be enabled later in this PR.) * Remove references to NANOPB_PROTOC_BIN Which wasn't being used, and wasn't pointing to a valid protoc. * Add ability to generate protos from cmake build. Currently, it's an entirely manual process via 'generate_protos' target. This target is not automatically run during a build. See Firestore/Protos/build-protos.sh for expected usage. * cleanup/update license in build-protos.sh * Build grpc proto sources (objc only) * Use 32bit nanopb fields (instead of 16) To match xcode build, but also to allow google/api/annotations.proto to compile. (A recent change to nanopb now enforces this.) This isn't strictly necessary, since we don't make use of that proto, so we could've simply removed it instead (and in fact, the objc protos do exactly that) but matching the xcode build certainly seems worthwhile. * Rebuild all proto sources * Skip whitespace checks on protoc generated files
156 lines
5.6 KiB
Objective-C
156 lines
5.6 KiB
Objective-C
/*
|
|
* Copyright 2018 Google
|
|
*
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
* you may not use this file except in compliance with the License.
|
|
* You may obtain a copy of the License at
|
|
*
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
*
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
* See the License for the specific language governing permissions and
|
|
* limitations under the License.
|
|
*/
|
|
|
|
// Generated by the protocol buffer compiler. DO NOT EDIT!
|
|
// source: google/rpc/status.proto
|
|
|
|
// This CPP symbol can be defined to use imports that match up to the framework
|
|
// imports needed when using CocoaPods.
|
|
#if !defined(GPB_USE_PROTOBUF_FRAMEWORK_IMPORTS)
|
|
#define GPB_USE_PROTOBUF_FRAMEWORK_IMPORTS 0
|
|
#endif
|
|
|
|
#if GPB_USE_PROTOBUF_FRAMEWORK_IMPORTS
|
|
#import <Protobuf/GPBProtocolBuffers.h>
|
|
#else
|
|
#import "GPBProtocolBuffers.h"
|
|
#endif
|
|
|
|
#if GOOGLE_PROTOBUF_OBJC_VERSION < 30002
|
|
#error This file was generated by a newer version of protoc which is incompatible with your Protocol Buffer library sources.
|
|
#endif
|
|
#if 30002 < GOOGLE_PROTOBUF_OBJC_MIN_SUPPORTED_VERSION
|
|
#error This file was generated by an older version of protoc which is incompatible with your Protocol Buffer library sources.
|
|
#endif
|
|
|
|
// @@protoc_insertion_point(imports)
|
|
|
|
#pragma clang diagnostic push
|
|
#pragma clang diagnostic ignored "-Wdeprecated-declarations"
|
|
|
|
CF_EXTERN_C_BEGIN
|
|
|
|
@class GPBAny;
|
|
|
|
NS_ASSUME_NONNULL_BEGIN
|
|
|
|
#pragma mark - RPCStatusRoot
|
|
|
|
/**
|
|
* Exposes the extension registry for this file.
|
|
*
|
|
* The base class provides:
|
|
* @code
|
|
* + (GPBExtensionRegistry *)extensionRegistry;
|
|
* @endcode
|
|
* which is a @c GPBExtensionRegistry that includes all the extensions defined by
|
|
* this file and all files that it depends on.
|
|
**/
|
|
@interface RPCStatusRoot : GPBRootObject
|
|
@end
|
|
|
|
#pragma mark - RPCStatus
|
|
|
|
typedef GPB_ENUM(RPCStatus_FieldNumber) {
|
|
RPCStatus_FieldNumber_Code = 1,
|
|
RPCStatus_FieldNumber_Message = 2,
|
|
RPCStatus_FieldNumber_DetailsArray = 3,
|
|
};
|
|
|
|
/**
|
|
* The `Status` type defines a logical error model that is suitable for different
|
|
* programming environments, including REST APIs and RPC APIs. It is used by
|
|
* [gRPC](https://github.com/grpc). The error model is designed to be:
|
|
*
|
|
* - Simple to use and understand for most users
|
|
* - Flexible enough to meet unexpected needs
|
|
*
|
|
* # Overview
|
|
*
|
|
* The `Status` message contains three pieces of data: error code, error message,
|
|
* and error details. The error code should be an enum value of
|
|
* [google.rpc.Code][google.rpc.Code], but it may accept additional error codes if needed. The
|
|
* error message should be a developer-facing English message that helps
|
|
* developers *understand* and *resolve* the error. If a localized user-facing
|
|
* error message is needed, put the localized message in the error details or
|
|
* localize it in the client. The optional error details may contain arbitrary
|
|
* information about the error. There is a predefined set of error detail types
|
|
* in the package `google.rpc` that can be used for common error conditions.
|
|
*
|
|
* # Language mapping
|
|
*
|
|
* The `Status` message is the logical representation of the error model, but it
|
|
* is not necessarily the actual wire format. When the `Status` message is
|
|
* exposed in different client libraries and different wire protocols, it can be
|
|
* mapped differently. For example, it will likely be mapped to some exceptions
|
|
* in Java, but more likely mapped to some error codes in C.
|
|
*
|
|
* # Other uses
|
|
*
|
|
* The error model and the `Status` message can be used in a variety of
|
|
* environments, either with or without APIs, to provide a
|
|
* consistent developer experience across different environments.
|
|
*
|
|
* Example uses of this error model include:
|
|
*
|
|
* - Partial errors. If a service needs to return partial errors to the client,
|
|
* it may embed the `Status` in the normal response to indicate the partial
|
|
* errors.
|
|
*
|
|
* - Workflow errors. A typical workflow has multiple steps. Each step may
|
|
* have a `Status` message for error reporting.
|
|
*
|
|
* - Batch operations. If a client uses batch request and batch response, the
|
|
* `Status` message should be used directly inside batch response, one for
|
|
* each error sub-response.
|
|
*
|
|
* - Asynchronous operations. If an API call embeds asynchronous operation
|
|
* results in its response, the status of those operations should be
|
|
* represented directly using the `Status` message.
|
|
*
|
|
* - Logging. If some API errors are stored in logs, the message `Status` could
|
|
* be used directly after any stripping needed for security/privacy reasons.
|
|
**/
|
|
@interface RPCStatus : GPBMessage
|
|
|
|
/** The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code]. */
|
|
@property(nonatomic, readwrite) int32_t code;
|
|
|
|
/**
|
|
* A developer-facing error message, which should be in English. Any
|
|
* user-facing error message should be localized and sent in the
|
|
* [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
|
|
**/
|
|
@property(nonatomic, readwrite, copy, null_resettable) NSString *message;
|
|
|
|
/**
|
|
* A list of messages that carry the error details. There is a common set of
|
|
* message types for APIs to use.
|
|
**/
|
|
@property(nonatomic, readwrite, strong, null_resettable) NSMutableArray<GPBAny*> *detailsArray;
|
|
/** The number of items in @c detailsArray without causing the array to be created. */
|
|
@property(nonatomic, readonly) NSUInteger detailsArray_Count;
|
|
|
|
@end
|
|
|
|
NS_ASSUME_NONNULL_END
|
|
|
|
CF_EXTERN_C_END
|
|
|
|
#pragma clang diagnostic pop
|
|
|
|
// @@protoc_insertion_point(global_scope)
|