-
-
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitLab support #246
GitLab support #246
Conversation
return dateFormatter | ||
} | ||
} | ||
|
||
private final class OptionalFractionalSecondsDateFormatter: DateFormatter { |
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.
GitLab returns the dates with milliseconds in it.
Looks that decoder.dateDecodingStrategy = .iso8601
doesn't support that, then I created a new dateFormatter that can be used in decoder.dateDecodingStrategy = .formatted
createdAt: Date(timeIntervalSince1970: 1558561570), | ||
updatedAt: Date(timeIntervalSince1970: 1558566949), | ||
closedAt: Date(timeIntervalSince1970: 1558566946), | ||
createdAt: Date(timeIntervalSince1970: 1_558_561_570), |
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.
swiftformat 馃し鈥嶁檪
8c1623d
to
99653a5
Compare
Can't find any info how to use it with gitlab? And does it support working with gitlab only (posting comment to gitlab MR's)? |
I'd look at the danger-js website for features - and ideally go bring some of those docs over to the swift site |
Currently GitLab support is affected by this issue though danger/danger-js#875, then could be that the usage of it won't return or (this is what I saw from my tests) returns after a while |
Fixes #247
馃帀