This repository has been archived by the owner on Jun 28, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 130
[PHP] Namespace inconsistency during deprecation #2141
Labels
lang: php
Issues specific to PHP.
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
🚨
This issue needs some love.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Comments
vchudnov-g
added
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
labels
Nov 12, 2018
@michaelbausor Updates? |
1 similar comment
@michaelbausor Updates? |
@michaelbausor any updates? |
No update at this time. |
@michaelbausor Could you provide an update and/or lower the priority if appropriate? |
This will be fixed in #2757 |
@hzyi-google Did #2757 fix this? If so could you close this issue? |
Fixed by #2757. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
lang: php
Issues specific to PHP.
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
🚨
This issue needs some love.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
We're trying to update the KMS client lib for PHP. The newly generated code is using a nicer namespace like
Google\Cloud\Kms\V1\CryptoKey\CryptoKeyPurpose
instead ofGoogle\Cloud\Kms\V1\CryptoKey_CryptoKeyPurpose
. Also the generator keeps the old namespaced class with a deprecation warning.This is a great feature, but we found there are some usages of old classes in various places.
Google\Cloud\Kms\V1\Gapic\KeyManagementServiceGapicClient
\Google\Cloud\Kms\V1\CryptoKey.php
\Google\Cloud\Kms\Tests\Unit\V1\KeyManagementServiceClientTest
For 1, this is the sample code in the doc comment, so it is basically telling users to use the deprecated class which will be removed with the next release. I think the sample code should use the newer class name.
For 2 and 3, I still think it is cleaner to use the newer namespace.
The text was updated successfully, but these errors were encountered: