You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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').
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.
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 tofindRepeaterRows()
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.
The text was updated successfully, but these errors were encountered: