#11 ALL_CAPS message fields are parsed incorrectly

Author: boukeversteegh

betterproto/tests/inputs/casing_message_field_uppercase/casing_message_field_uppercase.json

@@ -0,0 +1,3 @@
+{
+  "UPPERCASE": 10
+}

betterproto/tests/inputs/casing_message_field_uppercase/casing_message_field_uppercase.proto

@@ -0,0 +1,5 @@
+syntax = "proto3";
+
+message Test {
+  int32 UPPER_CAMEL_CASE = 1;
+}

betterproto/tests/inputs/casing_message_field_uppercase/casing_message_field_uppercase.py

@@ -0,0 +1,10 @@
+from betterproto.tests.output_betterproto.casing_message_field_uppercase.casing_message_field_uppercase import (
+    Test,
+)
+
+
+def test_message_casing():
+    message = Test()
+    assert hasattr(
+        message, "upper_camel_case"
+    ), "UPPER_CAMEL_CASE attribute is converted to upper_camel_case in python"

betterproto/tests/inputs/config.py

@@ -9,6 +9,7 @@
     "import_packages_same_name",
     "oneof_enum",
     "googletypes_service_returns_empty",
+    "casing_message_field_uppercase",
 }
 
 services = {