Skip to content
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

Further cleanup of Configuration model #67

Merged
merged 1 commit into from
Jul 31, 2024

Conversation

technoir42
Copy link

Remove properties that have no effect.

@@ -25,7 +22,6 @@ class TestCacheKeyFactory(
.use {
it.write(versionNameProvider.versionName)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can remove versionNameProvider.versionName as well? The version change shouldn't trigger test cache wipeout by itself. And if the apk will change then componentCachingKey will change as well.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The idea might've been for the cache key to depend on the version of Marathon itself, however versionName seems to always be unknown because there is no Implementation-Version: in the JAR manifest.

@technoir42 technoir42 merged commit bfa55f9 into develop Jul 31, 2024
2 checks passed
@technoir42 technoir42 deleted the further-configuration-cleanup branch July 31, 2024 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants