achilleasa / dart_amqp

93%

master: 93%

LAST BUILD ON BRANCH dont-use-null-check-op-on-potentially-null-value

branch: dont-use-null-check-op-on-potentially-null-value

CHANGE BRANCH

x

Reset

• dont-use-null-check-op-on-potentially-null-value
• add-support-for-tls-connections
• allow-clients-with-ro-access-to-skip-resource-declarations
• bump-version
• close-consumer-streams-when-handling-channel-exceptions
• fix-code-coverage-issues
• fix-formatting-warnings-in-tests
• fix-incorrect-handling-of-nowait-flag
• fix-lint-issues
• fix-reconnect-related-bugs
• fix-typo-in-readme
• implement-heartbeats
• master
• misc-dart2-compat-changes
• opt-to-null-safety-and-more-lint-fixes
• run-ci-on-pull-requests
• support-confirm
• support-per-consumer-qos
• support-registration-of-bad-cert-handler
• switch-to-dart-format
• switch-to-flutter-pub-invocations
• switch-to-gh-actions-for-ci
• track-missed-heartbeats
• tweak-ci-script
• update-api-docs
• update-part-of-directives

Build # 5870929547

Build Type

Pull #105

github

Committed by achilleasa

Commit Message

Don't use null check operator on potentially nil value in ConnectionClose message

This commit attempts to fix issue #104 by using a ?? operator to avoid
raising a _CastError if a ConnectionClose message does not include a
replyText field.

Pull Request Pull Request #105: Don't use null check operator on potentially nil value in ConnectionClose messsage

Run Details

1685 of 1811 relevant lines covered (93.04%)

1.58 hits per line