enum validation fails when enum defined in different package

[snowp]

Using the following validation

  envoy.common.ipc_metrics.kind.TrafficType traffic_type = 1 [(validate.rules).enum = {not_in: [0]}];

fails with

::TrafficType'?
        const std::set<TrafficType> _AtlasAccessLog_TrafficType_NotInLookup = {
                       ^~~~~~~~~~~
                       common::ipc_metrics::kind::TrafficType

Seems like the generated code is not including the fully qualified name of the enum type

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[akonradi]

@snowp is this still an issue? Is this for C++ only or other languages as well? Would you be able to work on a PR?

[snowp]

I haven't run into this issue recently so it might have gotten fixed for all I know. I only saw this in C++.

If I find the time I can try to reproduce this and work on a fix, but it's not high on my priorities.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[manuelnp]

I just suffered this issue, only in C++.

[anopheles]

The issue is also available within go, using following go release [email protected]

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[hurrycane]

I can confirm this is an issue -- no imports for enums defined in a different package.