Skip to content

Commit bcff4f8

Browse files
Protocol Buffer TeamLogofile
Protocol Buffer Team
authored and
Logofile
committed
Project import generated by Copybara.
PiperOrigin-RevId: 546298303 Change-Id: Icf2a0e62c5ac9a559311069615a245fd31069858
1 parent 3745ff4 commit bcff4f8

File tree

17 files changed

+146
-90
lines changed

17 files changed

+146
-90
lines changed

‎content/getting-started/cpptutorial.md‎

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -88,9 +88,10 @@ message Person {
8888
optional string email = 3;
8989
9090
enum PhoneType {
91-
MOBILE = 0;
92-
HOME = 1;
93-
WORK = 2;
91+
PHONE_TYPE_UNSPECIFIED = 0;
92+
PHONE_TYPE_MOBILE = 1;
93+
PHONE_TYPE_HOME = 2;
94+
PHONE_TYPE_WORK = 3;
9495
}
9596
9697
message PhoneNumber {
@@ -123,7 +124,7 @@ even define message types nested inside other messages -- as you can see, the
123124
`PhoneNumber` type is defined inside `Person`. You can also define `enum` types
124125
if you want one of your fields to have one of a predefined list of values --
125126
here you want to specify that a phone number can be one of the following phone
126-
types: `MOBILE`, `HOME`, or `WORK`.
127+
types: `PHONE_TYPE_MOBILE`, `PHONE_TYPE_HOME`, or `PHONE_TYPE_WORK`.
127128

128129
The " = 1", " = 2" markers on each element identify the unique field number that
129130
field uses in the binary encoding. Field numbers 1-15 require one less byte to

‎content/getting-started/csharptutorial.md‎

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -120,9 +120,10 @@ message Person {
120120
string email = 3;
121121
122122
enum PhoneType {
123-
MOBILE = 0;
124-
HOME = 1;
125-
WORK = 2;
123+
PHONE_TYPE_UNSPECIFIED = 0;
124+
PHONE_TYPE_MOBILE = 1;
125+
PHONE_TYPE_HOME = 2;
126+
PHONE_TYPE_WORK = 3;
126127
}
127128
128129
message PhoneNumber {
@@ -146,7 +147,8 @@ while the `AddressBook` message contains `Person` messages. You can even define
146147
message types nested inside other messages -- as you can see, the `PhoneNumber`
147148
type is defined inside `Person`. You can also define `enum` types if you want
148149
one of your fields to have one of a predefined list of values -- here you want
149-
to specify that a phone number can be one of `MOBILE`, `HOME`, or `WORK`.
150+
to specify that a phone number can be one of `PHONE_TYPE_MOBILE`,
151+
`PHONE_TYPE_HOME`, or `PHONE_TYPE_WORK`.
150152

151153
The " = 1", " = 2" markers on each element identify the unique "tag" that field
152154
uses in the binary encoding. Tag numbers 1-15 require one less byte to encode

‎content/getting-started/darttutorial.md‎

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -103,9 +103,10 @@ message Person {
103103
string email = 3;
104104
105105
enum PhoneType {
106-
MOBILE = 0;
107-
HOME = 1;
108-
WORK = 2;
106+
PHONE_TYPE_UNSPECIFIED = 0;
107+
PHONE_TYPE_MOBILE = 1;
108+
PHONE_TYPE_HOME = 2;
109+
PHONE_TYPE_WORK = 3;
109110
}
110111
111112
message PhoneNumber {
@@ -129,7 +130,8 @@ while the `AddressBook` message contains `Person` messages. You can even define
129130
message types nested inside other messages -- as you can see, the `PhoneNumber`
130131
type is defined inside `Person`. You can also define `enum` types if you want
131132
one of your fields to have one of a predefined list of values -- here you want
132-
to specify that a phone number can be one of `MOBILE`, `HOME`, or `WORK`.
133+
to specify that a phone number can be one of `PHONE_TYPE_MOBILE`,
134+
`PHONE_TYPE_HOME`, or `PHONE_TYPE_WORK`.
133135

134136
The " = 1", " = 2" markers on each element identify the unique "tag" that field
135137
uses in the binary encoding. Tag numbers 1-15 require one less byte to encode

‎content/getting-started/gotutorial.md‎

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -114,9 +114,10 @@ message Person {
114114
string email = 3;
115115
116116
enum PhoneType {
117-
MOBILE = 0;
118-
HOME = 1;
119-
WORK = 2;
117+
PHONE_TYPE_UNSPECIFIED = 0;
118+
PHONE_TYPE_MOBILE = 1;
119+
PHONE_TYPE_HOME = 2;
120+
PHONE_TYPE_WORK = 3;
120121
}
121122
122123
message PhoneNumber {
@@ -140,7 +141,8 @@ while the `AddressBook` message contains `Person` messages. You can even define
140141
message types nested inside other messages -- as you can see, the `PhoneNumber`
141142
type is defined inside `Person`. You can also define `enum` types if you want
142143
one of your fields to have one of a predefined list of values -- here you want
143-
to specify that a phone number can be one of `MOBILE`, `HOME`, or `WORK`.
144+
to specify that a phone number can be one of `PHONE_TYPE_MOBILE`,
145+
`PHONE_TYPE_HOME`, or `PHONE_TYPE_WORK`.
144146

145147
The " = 1", " = 2" markers on each element identify the unique "tag" that field
146148
uses in the binary encoding. Tag numbers 1-15 require one less byte to encode

‎content/getting-started/javatutorial.md‎

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -92,9 +92,10 @@ message Person {
9292
optional string email = 3;
9393
9494
enum PhoneType {
95-
MOBILE = 0;
96-
HOME = 1;
97-
WORK = 2;
95+
PHONE_TYPE_UNSPECIFIED = 0;
96+
PHONE_TYPE_MOBILE = 1;
97+
PHONE_TYPE_HOME = 2;
98+
PHONE_TYPE_WORK = 3;
9899
}
99100
100101
message PhoneNumber {
@@ -145,7 +146,7 @@ even define message types nested inside other messages -- as you can see, the
145146
`PhoneNumber` type is defined inside `Person`. You can also define `enum` types
146147
if you want one of your fields to have one of a predefined list of values --
147148
here you want to specify that a phone number can be one of the following phone
148-
types: `MOBILE`, `HOME`, or `WORK`.
149+
types: `PHONE_TYPE_MOBILE`, `PHONE_TYPE_HOME`, or `PHONE_TYPE_WORK`.
149150

150151
The " = 1", " = 2" markers on each element identify the unique "tag" that field
151152
uses in the binary encoding. Tag numbers 1-15 require one less byte to encode
@@ -313,9 +314,10 @@ The generated code includes a `PhoneType` Java 5 enum, nested within `Person`:
313314

314315
```java
315316
public static enum PhoneType {
316-
MOBILE(0, 0),
317-
HOME(1, 1),
318-
WORK(2, 2),
317+
PHONE_TYPE_UNSPECIFIED(0, 0),
318+
PHONE_TYPE_MOBILE(1, 1),
319+
PHONE_TYPE_HOME(2, 2),
320+
PHONE_TYPE_WORK(3, 3),
319321
;
320322
...
321323
}

‎content/getting-started/kotlintutorial.md‎

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -106,9 +106,10 @@ message Person {
106106
string email = 3;
107107
108108
enum PhoneType {
109-
MOBILE = 0;
110-
HOME = 1;
111-
WORK = 2;
109+
PHONE_TYPE_UNSPECIFIED = 0;
110+
PHONE_TYPE_MOBILE = 1;
111+
PHONE_TYPE_HOME = 2;
112+
PHONE_TYPE_WORK = 3;
112113
}
113114
114115
message PhoneNumber {
@@ -132,7 +133,8 @@ while the `AddressBook` message contains `Person` messages. You can even define
132133
message types nested inside other messages -- as you can see, the `PhoneNumber`
133134
type is defined inside `Person`. You can also define `enum` types if you want
134135
one of your fields to have one of a predefined list of values -- here you want
135-
to specify that a phone number can be one of `MOBILE`, `HOME`, or `WORK`.
136+
to specify that a phone number can be one of `PHONE_TYPE_MOBILE`,
137+
`PHONE_TYPE_HOME`, or `PHONE_TYPE_WORK`.
136138

137139
The " = 1", " = 2" markers on each element identify the unique "tag" that field
138140
uses in the binary encoding. Tag numbers 1-15 require one less byte to encode

‎content/getting-started/pythontutorial.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -86,9 +86,10 @@ message Person {
8686
optional string email = 3;
8787
8888
enum PhoneType {
89-
MOBILE = 0;
90-
HOME = 1;
91-
WORK = 2;
89+
PHONE_TYPE_UNSPECIFIED = 0;
90+
PHONE_TYPE_MOBILE = 1;
91+
PHONE_TYPE_HOME = 2;
92+
PHONE_TYPE_WORK = 3;
9293
}
9394
9495
message PhoneNumber {

‎content/news/2023-06-29.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ message Player {
135135
HANDED_AMBIDEXTROUS = 3,
136136
}
137137
138-
Handed handed = 4 [features.field_presence = IMPLICIT];
138+
Handed handed = 4;
139139
}
140140
```
141141

‎content/news/2023-07-06.md‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
+++
2+
title = "Changes Announced on July 6, 2023"
3+
weight = 21
4+
linkTitle = "July 6, 2023"
5+
toc_hide = "true"
6+
description = "Changes announced for Protocol Buffers on July 6, 2023."
7+
type = "docs"
8+
+++
9+
10+
## Dropping PHP 7.x Support
11+
12+
As per our official
13+
[PHP support policy](https://cloud.google.com/php/getting-started/supported-php-versions),
14+
we will be dropping support for PHP 7.4 and lower. This means the minimum
15+
supported PHP version is 8.0.
16+
17+
If you are running an older version of PHP, you can install a previous release
18+
of the protobuf PHP extension by running `pecl install protobuf-3.23.3`.
19+
20+
## Dropping Ruby 2.6 Support
21+
22+
As per our official
23+
[Ruby support policy](https://cloud.google.com/ruby/getting-started/supported-ruby-versions),
24+
we will be dropping support for Ruby 2.6 and lower. This means the minimum
25+
supported Ruby version is 2.7.
26+
27+
## Dropping Python 3.7 Support
28+
29+
As per our official
30+
[Python support policy](https://cloud.google.com/python/docs/supported-python-versions),
31+
we will be dropping support for Python 3.7 and lower. This means the minimum
32+
supported Python version is 3.8.

‎content/news/_index.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ type = "docs"
88
News topics provide information about past events and changes with Protocol
99
Buffers, and plans for upcoming changes.
1010

11+
* [July 6, 2023](/news/2023-07-06) - Dropping support
12+
for older versions of PHP, Ruby, and Python
1113
* [June 29, 2023](/news/2023-06-29) - Protobuf Editions
1214
announcement
1315
* [April 28, 2023](/news/2023-04-28) - Null no longer

0 commit comments

Comments
 (0)