1. 17 Jun, 2019 2 commits
  2. 21 May, 2019 5 commits
  3. 17 May, 2019 1 commit
  4. 10 May, 2019 1 commit
  5. 23 Apr, 2019 1 commit
  6. 27 Mar, 2019 1 commit
  7. 26 Mar, 2019 1 commit
  8. 25 Mar, 2019 2 commits
  9. 20 Mar, 2019 1 commit
  10. 13 Mar, 2019 2 commits
  11. 12 Mar, 2019 1 commit
  12. 06 Mar, 2019 1 commit
  13. 28 Feb, 2019 1 commit
  14. 25 Feb, 2019 1 commit
  15. 22 Feb, 2019 1 commit
  16. 21 Feb, 2019 1 commit
  17. 19 Feb, 2019 1 commit
  18. 16 Feb, 2019 2 commits
  19. 14 Feb, 2019 1 commit
  20. 07 Feb, 2019 1 commit
  21. 01 Feb, 2019 1 commit
  22. 31 Jan, 2019 1 commit
  23. 28 Jan, 2019 2 commits
  24. 25 Jan, 2019 1 commit
    • Paul Yang's avatar
      Allow internalAddGeneratedFile to depend on new nested message name (#5629) · 53a1d496
      Paul Yang authored
      Previously, internalAddGeneratedFile has to depend on old non-nested name for sub-messages.
      This creates a hard dependency on old generated code for compatibility usage.
      If user's code has custome error handler, the deprecation warning in the old generated code
      will also be thrown (even though users haven't explicitly depended on the old message name).
      
      To fix this problem, this change added an additional flag in the generated code to tell run
      time that it's safe to use new message name. In this way, internalAddGeneratedFile can safely
      depend on new name and don't trigger unnecessary deprecation warning.
      53a1d496
  25. 24 Jan, 2019 1 commit
  26. 23 Jan, 2019 1 commit
  27. 22 Jan, 2019 2 commits
  28. 18 Jan, 2019 1 commit
  29. 17 Jan, 2019 1 commit
  30. 08 Jan, 2019 1 commit