Incorrect order of nested messages generator

[qwetexac]

Description

Hey, while generating types from nested fields, the generator first looks for already defined top-level fields instead of looking for fields inside the parent. See example below:

message Metrics {
  uint64 foo = 1;
}

message Parent {
  message Metrics {
    uint64 bar = 1;
  }

  repeated Metrics items = 1;
}

Expected result

export function Metrics() {
    return [
        [1, "foo", "uint64", 1],
    ];
}

export function Parent_Metrics() {
    return [
        [1, "bar", "uint64", 1],
    ];
}

export function Parent() {
    return [
        [1, "items", ["repeated", Parent_Metrics], 1],
    ];
}

Actual result

export function Metrics() {
    return [
        [1, "foo", "uint64", 1],
    ];
}

export function Parent_Metrics() { // totally unused
    return [
        [1, "bar", "uint64", 1],
    ];
}

export function Parent() {
    return [
        [1, "items", ["repeated", Metrics], 1],
    ];
}

Soluiton

export const pathField = (field: string, base: string, out: MakeOuts, parent?: string) => {
  // ...rest code

+ const fieldPath = joinPath(field);
+ const fullPath = joinPath(base, field);

- if (out.names.has(field)) {
-   return joinPath(field);
- }

- return joinPath(base, field);

+ if (out.names.has(fullPath)) {
+   return fullPath;
+ }

+ if (out.names.has(fieldPath)) {
+   return fieldPath;
+ }

+ return fullPath;
};

This will tell the generator to search in nested messages before getting messages at the level above.