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

by.repeater to match virtual repeaters #2804

Closed
alecxe opened this issue Dec 26, 2015 · 3 comments
Closed

by.repeater to match virtual repeaters #2804

alecxe opened this issue Dec 26, 2015 · 3 comments

Comments

@alecxe
Copy link
Contributor

alecxe commented Dec 26, 2015

Referencing Virtual Repeater and Protractor SO post, can we improve by.repeater() locator to also match Angular material design virtual repeaters?

Since virtual repeaters don't support tracking, aliasing and other repeater micro-syntax, I think there is no harm to this improvement. From what I understand, the change should be in only adding a md-virtual prefix to findRepeaterRows() client side script function..

On the other hand, we might argue if other material design elements/features should be supported by Protractor in general.

Thank you.

@sjelin
Copy link
Contributor

sjelin commented Dec 28, 2015

I think maybe a separate repeater is in order.

Also, it might be good if there was an easy way to just add locators for arbitrary properties. Something like by.addSimpleLocator('virtualRepeater', 'md-virtual-repeat').

@juliemr, thoughts?

@juliemr
Copy link
Member

juliemr commented Dec 22, 2016

Sorry, I hadn't read this fully. I don't think we should support md-specific things - ideally, material design (or other libraries) would export page objects for dealing with their directives/components.

@alecxe
Copy link
Contributor Author

alecxe commented Dec 22, 2016

Okay, sure, thanks for getting back to this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants