-
Notifications
You must be signed in to change notification settings - Fork 247
Fix: CalendarComponent.AddProperty adds the CalendarProperty
#801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: CalendarComponent.AddProperty adds the CalendarProperty
#801
Conversation
Before the fix, only the `CalendarProperty.Value` was added. Resolves #797
Codecov ReportAll modified and coverable lines are covered by tests ✅ ❌ Your project status has failed because the head coverage (67%) is below the target coverage (80%). You can increase the head coverage or adjust the target coverage. @@ Coverage Diff @@
## main #801 +/- ##
===================================
Coverage 67% 67%
===================================
Files 106 106
Lines 4421 4421
Branches 1060 1060
===================================
+ Hits 2942 2943 +1
+ Misses 1042 1041 -1
Partials 437 437
... and 1 file with indirect coverage changes 🚀 New features to boost your workflow:
|
9893ad0 to
d7b3ef1
Compare
Remove duplicate of the test from SimpleDeserializationTests
| Assert.That(propDescription.Parameters.FirstOrDefault(p => p.Name == "FMTTYPE")!.Value, Is.EqualTo("text/html")); | ||
|
|
||
| Assert.That(propProjects.Parameters, Has.Count.EqualTo(2), "Parameter list should have 2 elements"); | ||
| Assert.That(propProjects.Value, Is.EqualTo("ProjectA,ProjectB")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should propProject.Values be a list containing ProjectA and ProjectB as elements?
|



Before the fix, only the
CalendarProperty.Valuewas added, andCalendarProperty.Parametersand other properties got lost.Resolves #797