-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[@kbn/expect] "fork" expect.js into repo #33761
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
Conversation
|
Pinging @elastic/kibana-operations |
This comment has been minimized.
This comment has been minimized.
💚 Build Succeeded |
|
Any consideration for moving to another assertion library that is supported? A codemod to replace expect.js with, say, chai, may not be super diffucult, and then we don't need a fork. |
|
@w33ble I'm not saying we can't do that, but I think it would probably be more productive to go through and finish migrating all the existing tests to Jest. Right now though I'm trying to collect assertion counts for the functional tests, which I don't think migrating to chai would help with. |
💚 Build Succeeded |
* [@kbn/expect] "fork" expect.js into repo * [eslint] autofix references to expect.js * [tslint] autofix all expect.js imports * now that expect.js is in strict mode, avoid reassigning fn.length
* [@kbn/expect] "fork" expect.js into repo * [eslint] autofix references to expect.js * [tslint] autofix all expect.js imports * now that expect.js is in strict mode, avoid reassigning fn.length
* [@kbn/expect] "fork" expect.js into repo * [eslint] autofix references to expect.js * [tslint] autofix all expect.js imports * now that expect.js is in strict mode, avoid reassigning fn.length
There are several improvements we'd like to make to expect.js, but the upstream repo is basically done. There are many open PRs and the last commit was in January 2015, so I think we should pull the library into our repo so we can tweak it.
Custom eslint/tslint rules are included to rewrite
import expect from 'expect.js'toimport expect from '@kbn/expect'.