-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
Allow nil GitHubMilestone descriptions #253
Allow nil GitHubMilestone descriptions #253
Conversation
The JSON parser breaks if there is a milestone associated with the PR, which has a blank/nil description.
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.
Thank you for the PR :)
Could you please update the CHANGELOG?
Also I would suggest to add another test to avoid the regression instead of replace the one we have, what do you think?
Sounds good! I initially had it as a separate test, will change it back and update the changelog. Thanks for taking a look 😁 |
Looks like |
If you merge master back should pass the CI now 👍 |
…tone_descriptions
Generated by 🚫 Danger Swift against d79af76 |
merge on green |
Sorry for being slow on the master-merge, thanks for the help @f-meloni! |
No problem :) |
The Problem
When
danger-swift
is executed on a PR that has a milestone associated with it, the JSON parsing will fail if the milestone'sdescription
field isnil
. JSON parsing fails with the following message:Proposed Solution
Since a
description
is an optional field for milestones, so too should it be optional in theGitHubMilestone
struct.