Branch event tag class update #45
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
EventTag class is implemented as a subclass. This allows the implementation of features in v1.3. Let's add the EventTag class to enable other members to start coding.
* branch-UG-Update: Update EventTag Class
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #45 +/- ##
============================================
- Coverage 69.54% 68.66% -0.89%
- Complexity 471 472 +1
============================================
Files 81 82 +1
Lines 1609 1634 +25
Branches 165 170 +5
============================================
+ Hits 1119 1122 +3
- Misses 447 469 +22
Partials 43 43 ☔ View full report in Codecov by Sentry. |
|
please approve this so that we can update the release Jar, which is counted for participation |
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.
Created event tag class as a subclass of eventtag.
I genuinely do not know how the other members are going to utilize this class, so I decide to keep the class simple.
The date-time is in "YYYY-mm-dd hh:mm:ss" format, but you can change it to your own likeing (please inform the team first).