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 500 #501
Fix 500 #501
Conversation
Pull Request Test Coverage Report for Build 3707937262
💛 - Coveralls |
@mauritsvanrees plone tests failed |
@jacadzaca This is a problem with
I have added a commit to your branch. |
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.
Thanks for fixing this!
@@ -18,7 +18,10 @@ New features: | |||
|
|||
Bug fixes: | |||
|
|||
- ... | |||
- vBoolean can now be used as an parameter |
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.
I think the fix covers all the property types... vInt
, vTime
, etc
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.
You're probably right, but I don't put things in the changelog if there isn't a corresponding test for the entry.
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.
If you put it in the changelog, it creates an expectation and then people come back if this is not the case. But since it is in the documentation, the expectation is there either way.
@@ -0,0 +1,9 @@ | |||
from icalendar import Event, vBoolean, vCalAddress | |||
|
|||
def test_vBoolean_can_be_used_as_parameter_issue_500(events): |
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 there be tests for some of the other types or is that excessive? Basically everything with an .to_ical()
method works and I'm assuming there's test already for those methods.
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.
There are tests for proper encoding for other v types, but I don't think there are any for checking if they can be used as a param. If you've got the time to file a PR with a parametrization of this test for other v types I'll gladly accept it :) if you don't, I will try to update the test sometime next week :)
elif isinstance(value, str): | ||
return dquote(value) | ||
else: | ||
return dquote(value.to_ical().decode(DEFAULT_ENCODING)) |
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.
The None return is interesting. When does it hit?
I see the tests running and from the conversation there arises no problem. I merge. The library is better than before. |
fix #500