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

test(chrome) Fix chrome tests for last versions #801

Merged
merged 2 commits into from
Jan 4, 2019
Merged

test(chrome) Fix chrome tests for last versions #801

merged 2 commits into from
Jan 4, 2019

Conversation

yarres
Copy link
Contributor

@yarres yarres commented Dec 19, 2018

Description

Update method names of some tests in /vg-api.spec.ts to allow compatibility with last versions of chrome in tests.
Update version of husky.

Checklist

  • I've read the (contributing)[https://github.com/videogular/videogular2/blob/master/CONTRIBUTING.md] guidelines
  • Code compiles correctly (run npm start)
  • Created tests (if necessary)
  • All tests passing (run npm test)
  • Extended the README / documentation (if necessary)

@Elecash
Copy link
Member

Elecash commented Jan 2, 2019

You're going to kill me...

You have to remove this from the commit message: BREAKING CHANGE: None that I am aware of

If you fill the "breaking change" question that will trigger a new major release since a breaking change has been detected by semantic release.

Can you remove that from both commit messages please?

Yoann Arres Lapoque added 2 commits January 4, 2019 10:21
…usky.

Fix tests with methods starting by 'webkit' to prevent errors on the last versions of chrome.
Fix some tests using methods starting by 'webkit' for passing successfully the tests. Update to
husky version.
@yarres
Copy link
Contributor Author

yarres commented Jan 4, 2019

Ok, done.

@Elecash Elecash merged commit fbbf1f5 into videogular:master Jan 4, 2019
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.

2 participants