Skip to content

Rename GemfireConstants to SpringGemFireConstants and introduce a new GemfireConstants [DATAGEODE-285] #330

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.

Sign up for GitHub

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

Jump to bottom
Open
spring-projects-issues opened this issue Dec 12, 2019 · 0 comments
Open

Rename GemfireConstants to SpringGemFireConstants and introduce a new GemfireConstants [DATAGEODE-285] #330

spring-projects-issues opened this issue Dec 12, 2019 · 0 comments
Labels
in: api Issues with API type: enhancement A general enhancement

Comments

@spring-projects-issues
Copy link

John Blum opened DATAGEODE-285 and commented

The naming of the GemfireConstants actually refers to constants (e.g. String literals) for Spring Data Geode bean names for Apache Geode resources and schema objects, such as Pools, Region types, etc.

 

This development task to improve on the naming conventions used and make the codebase more intuitive

No further details from DATAGEODE-285
@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: api Issues with API labels Dec 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
in: api Issues with API type: enhancement A general enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@spring-projects-issues