google-analytics-data-v1alpha 0.6.1 → 0.7.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 4f1f102c64905a1dbbb3ca35ea1f45a1b6715f77bf0f49b9145f959bddad0618
|
4
|
+
data.tar.gz: 66274a94ad9f6695a6edb528e6b1c120b99596c44289412499aab5f162bd0b9a
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 659e65666d5dd59f4fc212e5e0f3d300da171793ff947c1681af291bf65310de4355599e9f3d7ab1f53496870002db4f902bbe3e38d144de306f86b9f34c0025
|
7
|
+
data.tar.gz: ad58507a7c5868124381d7f2a43c14a26f9088e6fcc185f0c2e4dfb3a07d4d998b3d65e27c84919c546d2f870cd23f31bd640e2233247cc11ab4cba3ea585c37
|
data/README.md
CHANGED
@@ -6,6 +6,12 @@ The Google Analytics Data API provides programmatic methods to access report dat
|
|
6
6
|
|
7
7
|
https://github.com/googleapis/google-cloud-ruby
|
8
8
|
|
9
|
+
This gem is a _versioned_ client. It provides basic client classes for a
|
10
|
+
specific version of the Google Analytics Data V1alpha API. Most users should consider using
|
11
|
+
the main client gem,
|
12
|
+
[google-analytics-data](https://rubygems.org/gems/google-analytics-data).
|
13
|
+
See the section below titled *Which client should I use?* for more information.
|
14
|
+
|
9
15
|
## Installation
|
10
16
|
|
11
17
|
```
|
@@ -70,3 +76,61 @@ in security maintenance, and not end of life. Currently, this means Ruby 2.4
|
|
70
76
|
and later. Older versions of Ruby _may_ still work, but are unsupported and not
|
71
77
|
recommended. See https://www.ruby-lang.org/en/downloads/branches/ for details
|
72
78
|
about the Ruby support schedule.
|
79
|
+
|
80
|
+
## Which client should I use?
|
81
|
+
|
82
|
+
Most modern Ruby client libraries for Google APIs come in two flavors: the main
|
83
|
+
client library with a name such as `google-analytics-data`,
|
84
|
+
and lower-level _versioned_ client libraries with names such as
|
85
|
+
`google-analytics-data-v1alpha`.
|
86
|
+
_In most cases, you should install the main client._
|
87
|
+
|
88
|
+
### What's the difference between the main client and a versioned client?
|
89
|
+
|
90
|
+
A _versioned client_ provides a basic set of data types and client classes for
|
91
|
+
a _single version_ of a specific service. (That is, for a service with multiple
|
92
|
+
versions, there might be a separate versioned client for each service version.)
|
93
|
+
Most versioned clients are written and maintained by a code generator.
|
94
|
+
|
95
|
+
The _main client_ is designed to provide you with the _recommended_ client
|
96
|
+
interfaces for the service. There will be only one main client for any given
|
97
|
+
service, even a service with multiple versions. The main client includes
|
98
|
+
factory methods for constructing the client objects we recommend for most
|
99
|
+
users. In some cases, those will be classes provided by an underlying versioned
|
100
|
+
client; in other cases, they will be handwritten higher-level client objects
|
101
|
+
with additional capabilities, convenience methods, or best practices built in.
|
102
|
+
Generally, the main client will default to a recommended service version,
|
103
|
+
although in some cases you can override this if you need to talk to a specific
|
104
|
+
service version.
|
105
|
+
|
106
|
+
### Why would I want to use the main client?
|
107
|
+
|
108
|
+
We recommend that most users install the main client gem for a service. You can
|
109
|
+
identify this gem as the one _without_ a version in its name, e.g.
|
110
|
+
`google-analytics-data`.
|
111
|
+
The main client is recommended because it will embody the best practices for
|
112
|
+
accessing the service, and may also provide more convenient interfaces or
|
113
|
+
tighter integration into frameworks and third-party libraries. In addition, the
|
114
|
+
documentation and samples published by Google will generally demonstrate use of
|
115
|
+
the main client.
|
116
|
+
|
117
|
+
### Why would I want to use a versioned client?
|
118
|
+
|
119
|
+
You can use a versioned client if you are content with a possibly lower-level
|
120
|
+
class interface, you explicitly want to avoid features provided by the main
|
121
|
+
client, or you want to access a specific service version not be covered by the
|
122
|
+
main client. You can identify versioned client gems because the service version
|
123
|
+
is part of the name, e.g. `google-analytics-data-v1alpha`.
|
124
|
+
|
125
|
+
### What about the google-apis-<name> clients?
|
126
|
+
|
127
|
+
Client library gems with names that begin with `google-apis-` are based on an
|
128
|
+
older code generation technology. They talk to a REST/JSON backend (whereas
|
129
|
+
most modern clients talk to a [gRPC](https://grpc.io/) backend) and they may
|
130
|
+
not offer the same performance, features, and ease of use provided by more
|
131
|
+
modern clients.
|
132
|
+
|
133
|
+
The `google-apis-` clients have wide coverage across Google services, so you
|
134
|
+
might need to use one if there is no modern client available for the service.
|
135
|
+
However, if a modern client is available, we generally recommend it over the
|
136
|
+
older `google-apis-` clients.
|
@@ -142,7 +142,13 @@ module Google
|
|
142
142
|
|
143
143
|
# Create credentials
|
144
144
|
credentials = @config.credentials
|
145
|
-
|
145
|
+
# Use self-signed JWT if the scope and endpoint are unchanged from default,
|
146
|
+
# but only if the default endpoint does not have a region prefix.
|
147
|
+
enable_self_signed_jwt = @config.scope == Client.configure.scope &&
|
148
|
+
@config.endpoint == Client.configure.endpoint &&
|
149
|
+
!@config.endpoint.split(".").first.include?("-")
|
150
|
+
credentials ||= Credentials.default scope: @config.scope,
|
151
|
+
enable_self_signed_jwt: enable_self_signed_jwt
|
146
152
|
if credentials.is_a?(String) || credentials.is_a?(Hash)
|
147
153
|
credentials = Credentials.new credentials, scope: @config.scope
|
148
154
|
end
|
@@ -54,6 +54,12 @@ module Google
|
|
54
54
|
# This indicates that the field may be set once in a request to create a
|
55
55
|
# resource, but may not be changed thereafter.
|
56
56
|
IMMUTABLE = 5
|
57
|
+
|
58
|
+
# Denotes that a (repeated) field is an unordered list.
|
59
|
+
# This indicates that the service may provide the elements of the list
|
60
|
+
# in any arbitrary order, rather than the order the user originally
|
61
|
+
# provided. Additionally, the list's order may or may not be stable.
|
62
|
+
UNORDERED_LIST = 6
|
57
63
|
end
|
58
64
|
end
|
59
65
|
end
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: google-analytics-data-v1alpha
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.7.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Google LLC
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2021-
|
11
|
+
date: 2021-02-02 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: gapic-common
|
@@ -154,7 +154,9 @@ description: The Google Analytics Data API provides programmatic methods to acce
|
|
154
154
|
report data in Google Analytics App+Web properties. With the Google Analytics Data
|
155
155
|
API, you can build custom dashboards to display Google Analytics data, automate
|
156
156
|
complex reporting tasks to save time, and integrate your Google Analytics data with
|
157
|
-
other business applications.
|
157
|
+
other business applications. Note that google-analytics-data-v1alpha is a version-specific
|
158
|
+
client library. For most uses, we recommend installing the main client library google-analytics-data
|
159
|
+
instead. See the readme for more details.
|
158
160
|
email: googleapis-packages@google.com
|
159
161
|
executables: []
|
160
162
|
extensions: []
|