Closed nobodyiam closed 3 months ago
These updates centralize the versioning information of the Apollo server by introducing a new ApolloServer
class that holds a VERSION
constant. The changes across various components adjust references from a previous Apollo
class to the new ApolloServer
, ensuring consistency in version information used throughout the system. This reorganization aims to streamline version management and improve code maintainability.
File Path | Change Summary |
---|---|
.../constants/ApolloServer.java |
New file defining VERSION constant for Apollo server version. |
.../common/controller/ApolloInfoController.java .../portal/controller/SystemInfoController.java |
Updated to use ApolloServer.VERSION instead of Apollo.VERSION ; adjustments in imports and method refactoring. |
🐰✨
In the land of code and byte,
Where versions shift from day to night,
A rabbit hopped with keen foresight,
"Align the versions, make them right!"
NowApolloServer
shines so bright,
A beacon in the devs' plight.
🌟📚
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Attention: Patch coverage is 0%
with 5 lines
in your changes are missing coverage. Please review.
Project coverage is 50.25%. Comparing base (
a73d032
) to head (23b03cb
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
What's the purpose of this PR
fix the apollo version logic by reading the server version instead of the apollo-core version
Brief changelog
Follow this checklist to help us incorporate your contribution quickly and easily:
mvn clean test
to make sure this pull request doesn't break anything.CHANGES
log.Summary by CodeRabbit
SystemInfoController
initialization process.