🏗️ Client Service Implementation #119
Merged
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
Codecov Report
@@ Coverage Diff @@
## main #119 +/- ##
===========================================
- Coverage 99.94% 86.46% -13.48%
===========================================
Files 158 113 -45
Lines 11739 9172 -2567
===========================================
- Hits 11733 7931 -3802
- Misses 3 682 +679
- Partials 3 559 +556
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
1. Refined the Test cases on the agile.Board service
1. Refactored the Test Cases for the Board services implementing mocked interfaces using table-test driven cases
1. Removed the support for Go 1.13.x due it's causing problems with the testing framework 2. Added the Go 1.16.x, 1.17.x and 1.18.x on the workflow matrix
1. Refined the Test cases on the agile.Epic service
1. Implemented the library API using a custom HTTP client interface for mocking purposes. 2. Created the first test cases under Agile service.
1. Supports the versions 1.14, and 1.15 2. As of Go 1.16, the same functionality is now provided by package io or package os, and those implementations should be preferred in new code. See the specific function documentation for
1. Created the new ApplicationRoleService implementation under the ./jira/internal folder. 2. This implementation supports the Jira version 2 and 3 with the objective to avoid code replication 3. Moved the HTTPClient interface to the common services interfaces.
1. Create the interface called PermissionSchemeGrantConnector with the service method contract 2. Created the new implementation of the interface 3. Linked the new implementation with the v2 and v3 modules
1. Create the interface called ProjectConnector with the service method contract 2. Created the new implementation of the interface 3. Linked the new implementation with the v2 and v3 modules
1. Create the interface called ProjectCategoryConnector with the service method contract 2. Created the new implementation of the interface 3. Linked the new implementation with the v2 and v3 modules
1. Create the interface called ProjectComponentConnector with the service method contract 2. Created the new implementation of the interface 3. Linked the new implementation with the v2 and v3 modules
1. Create the interface called ProjectFeatureConnector with the service method contract 2. Created the new implementation of the interface 3. Linked the new implementation with the v2 and v3 modules
1. Create the interface called ProjectPermissionSchemeConnector with the service method contract 2. Created the new implementation of the interface 3. Linked the new implementation with the v2 and v3 modules
1. Create the interface called ProjectPropertyConnector with the service method contract 2. Created the new implementation of the interface 3. Linked the new implementation with the v2 and v3 modules
1. Create the interface called ProjectRoleConnector with the service method contract 2. Created the new implementation of the interface 3. Linked the new implementation with the v2 and v3 modules
1. Create the interface called ProjectTypeConnector with the service method contract 2. Created the new implementation of the interface 3. Linked the new implementation with the v2 and v3 modules
1. Create the interface called ProjectValidatorConnector with the service method contract 2. Created the new implementation of the interface 3. Linked the new implementation with the v2 and v3 modules
1. Create the interface called ProjectVersionConnector with the service method contract 2. Created the new implementation of the interface 3. Linked the new implementation with the v2 and v3 modules
1. Created the new implementation of the interface 2. Linked the new implementation with the v2 and v3 modules
1. Created the new implementation of the interface 2. Linked the new implementation with the v2 and v3 modules
1. Created the new implementation of the interface 2. Linked the new implementation with the v2 and v3 modules
ctreminiom
added
duplicate
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.
This PR contains the changes required to implement the service modularization, the service clients will be an independent Go module, enabling you to model service dependencies in your application, and independently control service client and feature updates. This reduces the individual module size. We take advantage of Go modules, which became the default development mode in Go 1.13 and follow the Go module versioning strategy.
Any feedback would be very appreciated