| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes #2511.
|
|\
| |
| | |
remove leading whitespace in C# xml comments
|
| | |
|
|/
|
|
|
| |
This change has already been made in google's repo.
Replicating the change here to unblock work on genproto.
|
|
|
|
|
|
|
|
| |
Swift generators should default to CamelCasing the proto package and prefixing
symbols with that, but this option allows developers to override that behavior
with something custom if they desire.
Fixes https://github.com/google/protobuf/issues/1833
|
|
|
|
|
|
| |
This seems to be necessary to prevent warnings in some compiler
configurations, particularly for tag numbers that are too large to fit
in a signed 32-bit int.
|
| |
|
|
|
|
|
|
|
|
|
| |
This affects cases with leading capital letters.
This breaks compatibility with previous C# releases, but
fixes compatibility with other implementations.
See #2278 for details.
|
| |
|
|
|
|
|
|
| |
[skip ci]
Change-Id: I1ba6f6372a08b5796570851336e1a548602f60da
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
(This still doesn't fix the conformance tests, but at least
we're now consistent with the C++ code.)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This check adds a few constraints on the way to build a project when we have
a proto file which imports another one. In particular, on projects which
build both C# and Java, it's easy to end up with exceptions like
Expected: included.proto but was src/main/protobuf/included.proto
A user may work around this issue, but it may add unnecessary constraints
on the layout of the project.
According to https://github.com/google/protobuf/commit/f3504cf3b1d456a843e8242fdee9ba0bf2991dc1#diff-ecb0b909ed572381a1c8d1994f09a948R309
it has already been considered to get rid of this check, for
similar considerations, and because it doesn't exist in the Java code
|
|\|
| |
| | |
Merge 3.0.0-GA into master
|
| | |
|
|/
|
|
|
| |
(This still doesn't fix the conformance tests, but at least
we're now consistent with the C++ code.)
|
|
|
|
|
|
| |
platform (#1727)
This also updates the version number to 3.0.0-beta4
|
|
|
|
|
|
|
| |
We now just perform the optimization within AddRange itself.
This is a breaking change in terms of "drop in the DLL", but is
source compatible, which should be fine.
|
|
|
|
| |
(Also fix a few more C# 6-isms.)
|
|
|
|
| |
This fixes issue #1730.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is the only call to TypeExtensions.IsValueType, so we can remove
that method, making the whole type conditionally compiled out for .NET 3.5
|
| |
|
|
|
|
| |
* Adding condition compiler symbol to support .NET 3.5
|
|
|
|
|
| |
This isn't useful to most users, but can be handy in advanced use cases,
as requested in #1465.
|
|
|
|
|
|
|
|
| |
This doesn't currently change the ordering in the implementation, but allows us to do so in the future.
We also need to change
https://developers.google.com/protocol-buffers/docs/reference/csharp-generated#singular
which states "Finally, unlike Dictionary<TKey, TValue>, MapField<TKey, TValue> preserves insertion order of entries."
(We can just remove that sentence, I think.)
|
|\
| |
| | |
Merge Beta 3 release branch into master
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Allow custom type URL prefixes in Any.Pack
|
| |
| |
| |
| |
| |
| | |
(And likewise ignore the prefix in unpack.)
Fixes issue #1459.
|
|/ |
|
|
|
|
|
| |
(There are documentation changes and new fields in descriptor.proto that have resulted
in changes to the serialized descriptor, but no breaking changes for C#.)
|
|
|
|
| |
(JSON parsing already does the right thing.)
|
|
|
|
| |
JSON tests fail, as we're not using OriginalNameAttribute yet.
|
|
|
|
|
|
|
|
|
|
| |
Overview of changes:
- A new C#-specific command-line option, legacy_enum_values to revert to the old behavior
- When legacy_enum_values isn't specified, we strip the enum name as a prefix, and PascalCase the value name
- A new attribute within the C# code so that we can always tell the original in-proto name
Regenerating the C# code with legacy_enum_values leads to code which still compiles and works - but
there's more still to do.
|
|\
| |
| | |
Introduce a new nuget package, Google.Protobuf.Tools, basically to contain protoc on multiple platforms.
|
| |
| |
| |
| |
| |
| |
| |
| | |
protoc on multiple platforms.
I've moved both protoc.exe and the proto files out of Google.Protobuf.
The .proto files aren't a slam-dunk, but it feels like they belong with protoc as you'd *use* them with protoc.
It's not clear to me whether we really need both an x86 and x64 version of protoc.exe, as x86 would work on 64-bit Windows anyway. Discuss :)
|
|/
|
|
|
|
|
|
| |
This makes no externally visible behavioral changes. Internally and non-behaviorally:
- We use a field (compiler-generated) to store the JsonName to avoid recomputing it repeatedly
- The documentation for JsonName is updated to reflect the meaning better
- Readonly autoprops and expression-bodied properties used where possible
|
| |
|
|
|
|
|
| |
Conflicts:
csharp/src/Google.Protobuf/JsonFormatter.cs
|
| |
|