Skip to content

chore: resolve a bunch of linter warnings, no logic changes#334

Merged
sighphyre merged 1 commit intomainfrom
chore/warning-cleanups
Dec 4, 2025
Merged

chore: resolve a bunch of linter warnings, no logic changes#334
sighphyre merged 1 commit intomainfrom
chore/warning-cleanups

Conversation

@sighphyre
Copy link
Copy Markdown
Member

Don't think this makes any logical changes but it stops my IDE screaming at me in a bunch of places

@coveralls
Copy link
Copy Markdown
Collaborator

Pull Request Test Coverage Report for Build 19922642557

Details

  • 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.7%) to 79.668%

Totals Coverage Status
Change from base Build 19334986078: 0.7%
Covered Lines: 2526
Relevant Lines: 3097

💛 - Coveralls


private static ConcurrentHashMap<String, LongAdder> initCounts = new ConcurrentHashMap<>();

private final UnleashMetricService metricService;
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

All handled by the EngineProxy

import org.slf4j.LoggerFactory;

public class UnleashMetricServiceImpl implements UnleashMetricService {
private static final Logger LOGGER = LoggerFactory.getLogger(UnleashMetricServiceImpl.class);
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Not used

@Override
public Future<Void> scheduleOnce(Runnable runnable) {
return (Future<Void>) executorService.submit(runnable);
return executorService.submit(
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Think this was just wrong but didn't matter because the result wasn't really used. Pretty sure this is correct but still won't matter

Linter stops freaking though, which is nice

@@ -23,9 +23,7 @@
import io.getunleash.util.UnleashConfig;
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Mostly a bunch of unuseds which don't impact the test runs in anyway

.thenReturn(new FlatResponse<Boolean>(false, null));
Unleash unleash = new DefaultUnleash(baseConfig, engineProxy);

@SuppressWarnings("unchecked")
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Think this is correct thing to do here. Mocking is runtime goop so I don't think this has a meaningful way to determine the type

@@ -1,4 +1,4 @@
package io.getunleash.integration;
package io.getunleash.streaming;
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Not sure why this was in the integration package. It's alone in there, doesn't match it's actual package structure and that doesn't follow the pattern for our test packages anyway

@sighphyre sighphyre enabled auto-merge (squash) December 4, 2025 08:42

this.config = unleashConfig;
this.featureRepository = engineProxy;
this.metricService = engineProxy;
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

All handled by the EngineProxy

But but..

Copy link
Copy Markdown

@daveleek daveleek left a comment

Choose a reason for hiding this comment

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

Cool, so primarily cleaning up a bunch of assigned but unused variables, with some additional cleanup sprinkled on top in tests. :shipit:

@sighphyre sighphyre merged commit 5ee6f56 into main Dec 4, 2025
10 checks passed
@sighphyre sighphyre deleted the chore/warning-cleanups branch December 4, 2025 08:49
@github-project-automation github-project-automation Bot moved this from New to Done in Issues and PRs Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants