Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.22%. Comparing base (c167439) to head (13a25b1).
Report is 3 commits behind head on main.

@@           Coverage Diff           @@
##             main     #593   +/-   ##
=======================================
  Coverage   86.22%   86.22%           
=======================================
  Files          14       14           
  Lines        2845     2845           
=======================================
  Hits         2453     2453           
  Misses        282      282           
  Partials      110      110           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Ja7ad is this breaking?
If yes, can you list the breaking changes for the users (in PR description)?
To be clear, I have not issue with breaking of course, we just need clarity.

@Ja7ad is this breaking?
If yes, can you list the breaking changes for the users (in PR description)?
To be clear, I have not issue with breaking of course, we just need clarity.

Based on issue, it's breaking changes.

I asked because I see you also changed the name of Apikey into APIKey, and it's not part of the issue. Is there any other changes?

I asked because I see you also changed the name of Apikey into APIKey, and it's not part of the issue. Is there any other changes?

Revert it?

@Ja7ad I'm not sure what you mean here
I want to know what are the breaking changes for users in this PR
Of course, there is the changes asked in the issues. But is there any other changes? I see in the PRs you also took the opportunity to change naming that are not asked in the issue. So now I'm asking if there is another other changes like this in the PR that are breaking for users? I need this information to deliver a clear changelogs

@Ja7ad I'm not sure what you mean here
I want to know what are the breaking changes for users in this PR
Of course, there is the changes asked in the issues. But is there any other changes? I see in the PRs you also took the opportunity to change naming that are not asked in the issue. So now I'm asking if there is another other changes like this in the PR that are breaking for users? I need this information to deliver a clear changelogs

I mean do you want revert name of "ApiKey"?

I mean do you want revert name of "ApiKey"?

No I don't want, I trust you on what are the best changes.
But I need you to be clear in the PR description about the changes you made, so that I can document it clearly in the changelogs

I mean do you want revert name of "ApiKey"?

No I don't want, I trust you on what are the best changes.
But I need you to be clear in the PR description about the changes you made, so that I can document it clearly in the changelogs

The word API is an abbreviation of three words and, in terms of naming convention, is better written as "API" instead of "Api".

Build succeeded:

• integration-tests (go current version)
• integration-tests (go latest version)
• linter