-
-
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
Fix the format and nullable of startDate and dueDate, introducing assignees property to GitLab #381
Conversation
Add tests for the formatter. Adjust the test related to the format and nullable changes.
@417-72KI Hi, thanks for viewing my pull request. Btw, I have noticed that CI failed due to this change SwiftDocOrg/swift-doc@dc1cac9#diff-37ca2dd15ca0f6b1b49e78db084ef5b9R1 , shall we pump up the the swift tools version or just keep it as it? |
👋 |
@f-meloni Hi :) |
Let me see if I can merge it for you :) |
My bad I though I merged fc2e5b2 to master, but is still on an open PR, sorry |
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.
Nice PR, thank you, I have just few minor comments :)
- Update the Package.resoved (updated by swift build)
(Resolved)Thanks for the advice! For the upgrade of the library, it works great on Xcode 12, but the KeyPath syntax seems causing build failures both on my local machine's Xcode 11.0 and couple of CI tasks. Do you have this kind of issue on your side? And after upgrade the library, I am running into and trying to solve some unexpected test failures related to The failure message is as following. Test case testParsesDiff()
Test case testChangeTypeForModified()
Test case testChangeTypeForRenamed()
Update
let lines = changes.components(separatedBy: "\n").dropFirst().filter { !$0.isEmpty }.map(parseLine) But still wonder why this is just came out from no where 🤔 I will keep dig into this see what I can do for this. Please share your idea if you guys have any 😃 UpdateAfter the investigation, I have find out that swiftformat is cleaning up the trailing whitespacing for us and that causes the test data producing empty lines and leads to the failure of the tests. |
@@ -143,6 +143,8 @@ final class GitDiffTests: XCTestCase { | |||
])) | |||
} | |||
|
|||
// swiftlint:disable all | |||
// swiftformat:disable all |
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.
// swiftlint:disable trailing_whitespace
// swiftformat:disable trimwhitespace
I could't get any effect by using this set of disable so I turn to use all instead in the end.
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 will have a look at this separately, probably will just use a swiftformat config
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.
yeah you are right, that might be the better way to solve this kind of issues!
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.
LGTM!
waiting for @f-meloni
No code changes at a4fd57f , two link references fixed at CHANGELOG. |
@@ -143,6 +143,8 @@ final class GitDiffTests: XCTestCase { | |||
])) | |||
} | |||
|
|||
// swiftlint:disable all | |||
// swiftformat:disable all |
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 will have a look at this separately, probably will just use a swiftformat config
Many thank you guys for the reviews, I have found there are still some issues related to GitLab and I will filing pull requests later on :) |
startDate
anddueDate
propertyMake them optional
GitLab may produce null value on those two properties.
The date format
The format of dueDate has become
yyyy-MM-dd
and which cause this error:assignees
propertyThe assignees array is exist in the JSON but we don't have a property for that. It is not convenient if some team need to add some rules while they are able to set multiple assignees on merge request.
Reference