-
Notifications
You must be signed in to change notification settings - Fork 26
Add KeyActions enum #455
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
Add KeyActions enum #455
Conversation
renamed Meilisearch's Task to MTask
This is awesome, thanks! Will give it a full review shortly and look to get both merged in (in preparation for a release once a few more breaking changes are compiled). |
print(error.localizedDescription) | ||
dump(error) | ||
XCTFail("Failed to create a key") | ||
keyExpectation.fulfill() |
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'm assuming this test is a "happy path", and as such we should remove this expectation fulfill, and the comment above which states "is expected to fail".
+ removed keyExpection and comment of KeyTest with unsupported action tests passing
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.
Will need to merge the other PR first @curquiza, but both should be good to go.
Let's not do a release yet though -- I'll work on some other tweaks soon as my cal frees up!
@MiaKoring |
Sorry @MiaKoring! With this PR we'll do both the MTask and KeyActions. CI will be working once you bring in latest changes, and so can get it merged. Thanks |
# Conflicts: # Tests/MeiliSearchIntegrationTests/Utils.swift
Tests are passing, if there is something else that needs to be done, let me know |
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.
All looking good. Ignore the linter error, I'll tweak SwiftLint in a separate PR as it's a little sensitive right now.
@Sherlouk I cannot merge with the linter error. Do you want to open a PR to remove the linting issue? we will merge this PR after |
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.
bors merge
Pull Request
Related issue
Fixes #418
What does this PR do?
PR checklist
Please check if your PR fulfills the following requirements: