He-Pin opened a new pull request, #1750:
URL: https://github.com/apache/pekko-connectors/pull/1750
### Motivation
Compilation produced warnings across Scala 2.13 and Scala 3 including:
- Unused imports in google-cloud-pub-sub, google-fcm, geode, s3
- Pattern match exhaustivity in mqtt-streaming (Scala 3 E029)
- Anonymous class duplication at inline site in geode (Scala 3 E197)
- Deprecated API usage in aws-spi-pekko-http, kinesis, solr
- Type inferred to Object/Any in amqp, influxdb, jms, jakartams, s3
- Name shadowing in jms and jakartams test specs
- Structural type inference in kinesis Valve
- Suspicious unqualified getClass call in google-cloud-storage
- Unchecked calls in AmqpFlowTest Java tests
- Pattern type more specialized than RHS in google-cloud-pub-sub-grpc
### Modification
- Remove unused imports across multiple modules
- Add `@nowarn` annotations for intentional deprecated API usage and pattern
match exhaustivity in MQTT session event flows
- Fix pattern match in MqttFrameStage to use `Left(_)` instead of unchecked
type pattern
- Add `@nowarn` for anonymous class duplication in LabelledGenericGeneric
- Replace deprecated `Stream` with `LazyList` in kinesis tests
- Add explicit type annotations (`Map[String, Any]`, `[Any]`) to fix type
inference warnings
- Rename shadowed pattern variables in JMS test specs
- Add explicit `ValveSwitch` type annotation in kinesis Valve
- Use `this.getClass` in GCStorageWiremockBase constructor
- Add `@SuppressWarnings("unchecked")` to Java test methods
- Update `@nowarn` filters in google-cloud-pub-sub-grpc ExampleApp
- Change `.recover` to `.recoverWith` in amqp test for correct Future
chaining
### Result
Clean compilation with zero warnings across all Scala versions.
### Tests
- `sbt +test:compile` - all versions pass with no warnings
### References
None - code quality improvement
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
