-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Improve readability of CloudFoundryVcapEnvironmentPostProcessor by removing constants #45855
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for the proposal. The use of constants in this class is certainly a bit inconsistent at the moment. For example, we have Flagging for team attention to see which direction we should go in:
|
Thanks for the thoughtful feedback. I'm happy to follow whatever direction the team decides. |
I'd remove both existing constants from |
@wonyongg could you please update your PR to remove the existing constants rather than introducing a new one? |
This commit removes the VCAP_APPLICATION, VCAP_SERVICES, and VCAP_PROPERTY_SOURCE_NAME constants from the CloudFoundryVcapEnvironmentPostProcessor class, replacing them with string literals. This change simplifies the code and aligns with the team's decision to avoid using constants in this context. Signed-off-by: wonyongg <[email protected]>
@wilkinsona Please have a look when you have time—I'd really appreciate your review. Thank you! |
This commit removes the VCAP_APPLICATION and VCAP_SERVICES constants from the CloudFoundryVcapEnvironmentPostProcessor class, replacing them with string literals. See gh-45855 Signed-off-by: wonyongg <[email protected]>
Thanks @wonyongg ! |
This pull request extracts the hardcoded "vcap" string into a named constant
(
VCAP_PROPERTY_SOURCE_NAME
) within theCloudFoundryVcapEnvironmentPostProcessor
class.This is a minor internal refactoring and does not affect runtime behaviour.