Kraigo notifications

[myConsciousness]

1. Description

1.1. Checklist

• The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
• I have read the Contributor Guide and followed the process outlined for submitting PRs.
• I have updated/added tests for ALL new/updated/fixed functionality.
• I have updated/added relevant documentation in docs and added dartdoc comments with ///.
• I have updated/added relevant examples in examples.

1.2. Breaking Change

• Yes, this is a breaking change.
• No, this is not a breaking change.

1.3. Related Issues

[myConsciousness]

bors merge

[codecov-commenter]

Codecov Report

Merging #122 (347410d) into main (c027916) will increase coverage by 0.58%.
The diff coverage is 100.00%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@            Coverage Diff             @@
##             main     #122      +/-   ##
==========================================
+ Coverage   72.14%   72.72%   +0.58%     
==========================================
  Files          97       99       +2     
  Lines        1034     1056      +22     
==========================================
+ Hits          746      768      +22     
  Misses        288      288              

Impacted Files	Coverage Δ
lib/src/service/entities/notification.dart	100.00% <100.00%> (ø)
...ice/v1/notifications/notifications_v1_service.dart	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[bors]

Build succeeded:

• analyzer
• test

[myConsciousness]

Hi @Kraigo ,

Thanks for your contributions! These commits will be released as v0.4.0. :)

[Kraigo]

Hey, @myConsciousness why do you need every time test rate limit and authorization response for each request?
I see that is stubbed data which comes from BaseService and all method use that solution.
An endpoint methods should test for available parameters and expected response object.
Did I miss something? What cases can such a case cover?

[myConsciousness]

Hi @Kraigo ,

These are tests to ensure that each endpoint can reliably handle exception cases :) An exception case that endpoint A can handle perfectly and endpoint B returns a different exception or error would create chaos.

The processing in this package is commonized like a framework, but it’s up to the implementer to be able to use and implement it correctly. So, even if the code is redundant, these common specifications must be tested to ensure their correctness :)