- 04 May, 2016 1 commit
-
-
Nicolas "Pixel" Noble authored
-
- 30 Apr, 2016 1 commit
-
-
Nicolas "Pixel" Noble authored
-
- 29 Apr, 2016 1 commit
-
-
Nicolas "Pixel" Noble authored
-
- 27 Apr, 2016 1 commit
-
-
Adam Cozzette authored
This fixes the test_acts_likes_an_array test in RepeatedFieldTest, which checks that repeated fields respond to the same methods as regular Ruby arrays. The bsearch_index and dig array methods seem to be new in Ruby 2.3 and so we should support those.
-
- 22 Apr, 2016 1 commit
-
-
Josh Haberman authored
-
- 15 Apr, 2016 3 commits
-
-
Josh Haberman authored
-
Josh Haberman authored
-
Josh Haberman authored
For JSON encoding we provide a new option to decide at encode time whether to use camelCase or original proto field names: json = MapMessage.encode_json(m, :preserve_proto_fieldnames => true)
-
- 14 Apr, 2016 2 commits
-
-
Josh Haberman authored
-
Josh Haberman authored
The flags are: UPB_JSON_ACCEPT_LEGACY_FIELD_NAMES UPB_JSON_WRITE_LEGACY_FIELD_NAMES The first just allows the parser to accept the old field names. The second makes the printer print the old field names. These flags are intended to be temporary, as a migration aid for users.
-
- 03 Mar, 2016 1 commit
-
-
Josh Haberman authored
-
- 18 Feb, 2016 2 commits
-
-
Josh Haberman authored
-
Josh Haberman authored
-
- 10 Feb, 2016 1 commit
-
-
Josh Haberman authored
-
- 05 Feb, 2016 2 commits
-
-
Nicolas "Pixel" Noble authored
-
Nicolas "Pixel" Noble authored
-
- 04 Feb, 2016 2 commits
-
-
Josh Haberman authored
-
Josh Haberman authored
-
- 03 Feb, 2016 1 commit
-
-
Dongjoon Hyun authored
-
- 12 Jan, 2016 3 commits
-
-
Josh Haberman authored
-
Josh Haberman authored
-
Josh Haberman authored
-
- 21 Dec, 2015 2 commits
- 23 Nov, 2015 1 commit
-
-
Anders Carling authored
-
- 20 Nov, 2015 3 commits
-
-
Anders Carling authored
-
Anders Carling authored
-
Anders Carling authored
More informative and more ruby-like
-
- 28 Sep, 2015 1 commit
-
-
Josh Haberman authored
Also updated the Gemfile.lock since alpha-4 has been pushed to RubyGems. Change-Id: I8ddc5f125f28aa9a33c88dfe48251a75a877e1d3
-
- 27 Aug, 2015 1 commit
-
-
Feng Xiao authored
-
- 26 Aug, 2015 1 commit
-
-
Feng Xiao authored
Protoc, C++ runtime and Java runtime are updated to v3.0.0-beta-1, other languages are updated to v3.0.0-alpha-4.
-
- 20 Aug, 2015 1 commit
-
-
Josh Haberman authored
Change-Id: I6cf77f01370204ad4bc7b345a040a9a3de1706a0
-
- 13 Aug, 2015 1 commit
-
-
Josh Haberman authored
Change-Id: Ief77de7134e05e07b1a7e3970d49880c2d5e6fe9
-
- 17 Jul, 2015 2 commits
-
-
Josh Haberman authored
Change-Id: If7b1cc0f03f609a7f43ddafc8509b44207c60910
-
Josh Haberman authored
Change-Id: Id008ebac5159f773e1bde8b85acb2626cbd16de8
-
- 16 Jul, 2015 1 commit
-
-
Josh Haberman authored
This involved fixing a few important bugs in the Ruby implementation -- mostly cases of mixing upb field types and descriptor types (upb field types do not distinguish between int/sint/fixed/sfixed like descriptor types do). Also added protobuf-specific exceptions so parse errors can be caught specifically. Change-Id: Ib49d3db976900b2c6f3455c8b88af52cfb86e036
-
- 10 Jul, 2015 1 commit
-
-
Josh Haberman authored
While we are C99 in general, the Ruby build system for building C extensions enables several flags that throw warnings for C89/C90 variable ordering rules. To avoid spewing a million warnings (or trying to specifically override these warnings with command-line flags, which would be tricky and possibly fragile) we conform to Ruby's world of C89/C90. Change-Id: I0e03e62d95068dfdfde112df0fb16a248a2f32a0
-
- 08 Jul, 2015 1 commit
-
-
Josh Haberman authored
Change-Id: I8e2b425f9008e6b82d41d59783bb8b04af1f886f Fixes: https://github.com/google/protobuf/issues/474.
-
- 23 Jun, 2015 1 commit
- 09 Jun, 2015 1 commit
-
-
Josh Haberman authored
upb no longer requires -std=c99 but the Ruby/C code still uses C99 features.
-