File tree Expand file tree Collapse file tree 11 files changed +28
-31
lines changed Expand file tree Collapse file tree 11 files changed +28
-31
lines changed Load Diff Large diffs are not rendered by default.
Load Diff Large diffs are not rendered by default.
Original file line number Diff line number Diff line change 137
137
both variable-length encoding and fixed sizes. You can also create your own
138
138
composite data types by defining messages that are, themselves, data types that
139
139
you can assign to a field. In addition to the simple and composite value types,
140
- several < a href =/programming-guides /dos-donts#common > common types</ a >
140
+ several < a href =/best-practices /dos-donts#common > common types</ a >
141
141
are published.</ p > < h2 id =history > History</ h2 > < p > To read about the history of the protocol buffers project, see
142
142
< a href =/history > History of Protocol Buffers</ a > .</ p > < h2 id =philosophy > Protocol Buffers Open Source Philosophy</ h2 > < p > Protocol buffers were open sourced in 2008 as a way to provide developers
143
143
outside of Google with the same benefits that we derive from them internally. We
Original file line number Diff line number Diff line change
1
+ <!doctype html> < html lang =en > < head > < title > https://protobuf.dev/best-practices/1-1-1/</ title >
2
+ < link rel =canonical href =https://protobuf.dev/best-practices/1-1-1/ > < meta name =robots content ="noindex "> < meta charset =utf-8 > < meta http-equiv =refresh content ="0; url=https://protobuf.dev/best-practices/1-1-1/ "> </ head > </ html >
Original file line number Diff line number Diff line change
1
+ <!doctype html> < html lang =en > < head > < title > https://protobuf.dev/best-practices/api/</ title >
2
+ < link rel =canonical href =https://protobuf.dev/best-practices/api/ > < meta name =robots content ="noindex "> < meta charset =utf-8 > < meta http-equiv =refresh content ="0; url=https://protobuf.dev/best-practices/api/ "> </ head > </ html >
Original file line number Diff line number Diff line change
1
+ <!doctype html> < html lang =en > < head > < title > https://protobuf.dev/best-practices/dos-donts/</ title >
2
+ < link rel =canonical href =https://protobuf.dev/best-practices/dos-donts/ > < meta name =robots content ="noindex "> < meta charset =utf-8 > < meta http-equiv =refresh content ="0; url=https://protobuf.dev/best-practices/dos-donts/ "> </ head > </ html >
Original file line number Diff line number Diff line change 364
364
< a href =/reference/protobuf/textformat-spec > proto text format</ a >
365
365
to store your protocol buffer messages, the changes that you can make in your
366
366
proto definition are different.</ div > < p > Check
367
- < a href =/programming-guides /dos-donts > Proto Best Practices</ a > and
368
- the following rules:</ p > < ul > < li > Don’t change the field numbers for any existing fields. “Changing” the field
367
+ < a href =/best-practices /dos-donts > Proto Best Practices</ a > and the
368
+ following rules:</ p > < ul > < li > Don’t change the field numbers for any existing fields. “Changing” the field
369
369
number is equivalent to deleting the field and adding a new field with the
370
370
same type. If you want to renumber a field, see the instructions for
371
371
< a href =#deleting > deleting a field</ a > .</ li > < li > If you add new fields, any messages serialized by code using your “old”
Original file line number Diff line number Diff line change 396
396
< a href =/reference/protobuf/textformat-spec > proto text format</ a >
397
397
to store your protocol buffer messages, the changes that you can make in your
398
398
proto definition are different.</ div > < p > Check
399
- < a href =/programming-guides /dos-donts > Proto Best Practices</ a > and
400
- the following rules:</ p > < ul > < li > Don’t change the field numbers for any existing fields. “Changing” the field
399
+ < a href =/best-practices /dos-donts > Proto Best Practices</ a > and the
400
+ following rules:</ p > < ul > < li > Don’t change the field numbers for any existing fields. “Changing” the field
401
401
number is equivalent to deleting the field and adding a new field with the
402
402
same type. If you want to renumber a field, see the instructions for
403
403
< a href =#deleting > deleting a field</ a > .</ li > < li > Any new fields that you add should be < code > optional</ code > or < code > repeated</ code > . This means
Original file line number Diff line number Diff line change 378
378
< a href =/reference/protobuf/textformat-spec > proto text format</ a >
379
379
to store your protocol buffer messages, the changes that you can make in your
380
380
proto definition are different.</ div > < p > Check
381
- < a href =/programming-guides /dos-donts > Proto Best Practices</ a > and
382
- the following rules:</ p > < ul > < li > Don’t change the field numbers for any existing fields. “Changing” the field
381
+ < a href =/best-practices /dos-donts > Proto Best Practices</ a > and the
382
+ following rules:</ p > < ul > < li > Don’t change the field numbers for any existing fields. “Changing” the field
383
383
number is equivalent to deleting the field and adding a new field with the
384
384
same type. If you want to renumber a field, see the instructions for
385
385
< a href =#deleting > deleting a field</ a > .</ li > < li > If you add new fields, any messages serialized by code using your “old”
Load Diff Large diffs are not rendered by default.
You can’t perform that action at this time.
0 commit comments