Skip to content
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

Prepare protractor helper to work with async await #25

Closed

Conversation

wlsf82
Copy link
Owner

@wlsf82 wlsf82 commented Jan 5, 2019

Description

This PR updates the lib to be prepared to work with async/await, and it is related to issue #21.

Pull Request Checklist

  • Have you followed the steps in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Have you successfully run tests with your changes locally?
  • Have you written new tests for your changes, if necessary? (No new tests were needed.)
  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you made improvements to the documentation, if necessary? (docs/ folder and README.md)
  • Have you linked the correct GitHub issue, if there is any?

Other comments

@wlsf82
Copy link
Owner Author

wlsf82 commented Jan 6, 2019

@PauloGoncalvesBH, o BCH falhou, mas revise mesmo assim, please.

@wlsf82 wlsf82 force-pushed the prepare-protractor-helper-to-work-with-async-await branch from 68787e2 to ecd7063 Compare January 8, 2019 12:29
@PauloGoncalvesBH
Copy link
Collaborator

All the commits done so far are ok.

@PauloGoncalvesBH
Copy link
Collaborator

Suggestion: Add the keyword testing on package.json file.
This is necessary to be one of the projects suggested in the topic 'testing' of npmjs.com.

This is necessary to be one of the projects suggested in the topic
'testing' on npmjs.com.
@wlsf82
Copy link
Owner Author

wlsf82 commented Jan 9, 2019

@PauloGoncalvesBH, I've just pushed the code with your suggestion. Back to you.

@PauloGoncalvesBH
Copy link
Collaborator

@PauloGoncalvesBH, I've just pushed the code with your suggestion. Back to you.

The commit daa8e68 is ok also.
We need analyze the BCH result.

@PauloGoncalvesBH
Copy link
Collaborator

Let's make this adjustment in another PR.

wlsf82 pushed a commit that referenced this pull request Apr 1, 2019
protractor-helper is still not compatible with protractor v6

Waiting on #25
wlsf82 pushed a commit that referenced this pull request Apr 3, 2019
protractor-helper is still not compatible with protractor v6

Waiting on #25
wlsf82 pushed a commit that referenced this pull request Apr 16, 2019
protractor-helper is still not compatible with protractor v6

Waiting on #25
@wlsf82
Copy link
Owner Author

wlsf82 commented Dec 13, 2019

I'm closing this PR without merging since it's super outdated and it has too many conflicts. I may use some of its implementations in the new one when addressing issue #21 again.

@wlsf82 wlsf82 closed this Dec 13, 2019
@wlsf82 wlsf82 deleted the prepare-protractor-helper-to-work-with-async-await branch June 24, 2020 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants