APIs that introduce resource name message configurations to their GAPIC yaml will lose the format-* methods that format resource names. So as to not break clients, we have to reintroduce these methods.
APIs affected:
Steps to fix:
Ideally we would deprecate these formatting functions, so in the next major version we wouldn't have them at all, since ResourceName classes are superior in static-type-checking and usability.
APIs that introduce resource name message configurations to their GAPIC yaml will lose the
format-*methods that format resource names. So as to not break clients, we have to reintroduce these methods.APIs affected:
Steps to fix:
Ideally we would deprecate these formatting functions, so in the next major version we wouldn't have them at all, since ResourceName classes are superior in static-type-checking and usability.