[THEjacob1000]

Internal change only

[LOKE-XXXX]

Generated Go clients now have nil-safe getters for optional fields that #39 turns into pointers. Inspired by Go protobuf scalar getters: pointers track presence; getters return values or defaults. Callers that don't need to distinguish absence from a zero value can use Get<Field>(), including on a nil receiver, instead of repeating nil checks.

Getters are also generated for object definitions reached through refs. Names that collide with existing fields or getters gain an underscore suffix, preserving the existing field names and keeping the generated client compilable.

This stacks on #39. Consumers can adopt getters where zero-value fallback is appropriate and keep checking the pointer where presence matters; the JSON format stays unchanged.

Related PRs

• fix(lokerpc/codegen): pointerize optional scalar fields in go output #39

Screenshots / Videos

I have:

• Run and tested the code and provided clear evidence of this above
• Self reviewed the code and removed extraneous comments, debug logging, checked code style
• Listed any dependant PRs required for this change
• Added tests where practical and possible
• Documented a way to roll this change back if it is more than a code revert

all the above must be ticked

[smithamax]

Why

[smithamax]

I don't see how this solves anything related to the parent PR

[THEjacob1000]

it doesn't fix anything, the pointers do. getters are just qol so callers that don't care about presence can do f.GetName() instead of nil-checking every optional field, same as proto's GetX(). anything that needs to know if a field was sent still checks f.Name != nil