Rename API packages #1332
Merged
Rename API packages #1332
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
josecelano
added
Code Cleanup / Refactoring
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #1332 +/- ##
===========================================
+ Coverage 81.41% 81.43% +0.01%
===========================================
Files 230 230
Lines 16358 16358
Branches 16358 16358
===========================================
+ Hits 13318 13321 +3
Misses 2805 2805
+ Partials 235 232 -3 ☔ View full report in Codecov by Sentry. |
To avoid future conflicts with other API implementations like GraphQL API.
josecelano
force-pushed
the
1317-refactor-packages-rename-rest-tracker-api-packages
branch
from
c355c5e to
d190fee
Compare
|
ACK d190fee |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rename API packages to avoid future conflicts with other API implementations like GraphQL API.