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 definitions for angular-protractor 1.0.0-rc4 #2513
Conversation
@BillArmstrong would love you opinion on this please |
I've reviewed the changes and they look good with these exceptions:
Bill |
@isibner can you review Bill's comments please. Thanks. |
* Remove optional parameters from Element interface * Remove additional parameters from ElementFinder.isElementPresent * Add "asElementFinders_" and "then" methods to ElementArrayFinder interface
Sorry, I wasn't able to get to this yesterday! @BillArmstrong, thanks for the feedback - I've taken another look and your concerns were correct. The new commit should have fixes for everything you noted. |
Yup. Thanks @isibner / @BillArmstrong ! |
Add definitions for angular-protractor 1.0.0-rc4
I just pulled this (using "tsd query angular-protractor -a install"), and VisualStudio now gives me the following error: "Error 340 Subsequent variable declarations must have the same type. Variable '$' must be of type 'cssSelectorHelper', but here has type 'JQueryStatic'. [x]\Scripts\typings\jquery\jquery.d.ts 3936 I believe this is because I have included both jquery.d.ts and angular-protractor.d.ts in the same Visual Studio project, both of which declares the global variable "$". From Angular-protracor.d.ts If I'm not doing something wrong, this has to be a serious problem I believe? |
Possibly. The definitions are correct though. Protractor's
Don't use protractor and jQuery defs in the same project. More like a question for Visual Studio team. |
I've been working on a Typescript project that uses Angular/Protractor, so I've changed the definitions to match the latest Protractor version! There were a lot of API changes for the first major release, so this should make things a lot easier for Angular devs working with the library.