21

I'm using the latest protobuf.js with Node.js 4.4.5.

I currently struggle to get protobuf.js to output the string definitions of enums instead of integers. I tried several suggestions, but none of them worked:

I guess it's because of API changes in protobuf.js for the first one. For the second one, I can use the suggested solution partially, but if the message is nested within other messages, the builder seems to fall back to using the integer values, although the string values have been explicitly set.

Ideally, I'd like to overwrite the function which is used for producing the enum values, but I have a hard time finding the correct one with the debugger. Or is there a better way to achieve this for deeply nested objects?

Tobi
  • 31,405
  • 8
  • 58
  • 90

2 Answers2

4

The generated JS code from protoc has a map in one direction only e.g.

 proto.foo.Bar.Myenum = {
  HEY: 0,
  HO: 1
};

Rationale for this is here but you have to the reverse lookup in your own JS code. There are lots of easy solutions for this. I used the one at https://stackoverflow.com/a/59360329/449347 i.e.

Generic reverse mapper function ...

 export function getKey(map, val) {
  return Object.keys(map).find(key => map[key] === val);
}

UT ...

import { Bar } from "js/proto/bar_pb";

expect(getKey(proto.foo.Bar.Myenum, 0)).toEqual("HEY");
expect(getKey(proto.foo.Bar.Myenum, 1)).toEqual("HO");
expect(getKey(proto.foo.Bar.Myenum, 99)).toBeUndefined();
k1eran
  • 4,492
  • 8
  • 50
  • 73
0

Now you can use something like this

import { proto3 } from "@bufbuild/protobuf";

function get(v) {
    const texts = proto3.getEnumType(SomeEnumType).values.filter((v) => v.no === v);
    if (texts && texts.length > 0) {
      return texts[0].name;
    } else {
      return "Unknown";
    }
}
Bryan
  • 151
  • 1
  • 7