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.

Sign up for GitHub

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

Jump to bottom

The toString function should return native string for overridden descriptor accessors #1713

Closed
LavrovArtem opened this issue Aug 8, 2018 · 1 comment
Closed

The toString function should return native string for overridden descriptor accessors #1713

LavrovArtem opened this issue Aug 8, 2018 · 1 comment
Assignees
@LavrovArtem
Labels
!IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug

Comments

@LavrovArtem
Copy link
Contributor

see DevExpress/testcafe#2707
@LavrovArtem LavrovArtem added this to the Sprint #15 milestone Aug 8, 2018
@LavrovArtem LavrovArtem self-assigned this Aug 8, 2018
LavrovArtem added a commit to LavrovArtem/testcafe-hammerhead that referenced this issue Aug 8, 2018
@LavrovArtem
fix `The toString function should return native string for overridden…
1dc43df 
… descriptor accessors` (close DevExpress#1713)
@AndreyBelym AndreyBelym mentioned this issue Sep 10, 2018
Closed
AndreyBelym pushed a commit to AndreyBelym/testcafe-hammerhead that referenced this issue Feb 28, 2019
@LavrovArtem @AndreyBelym
fix `The toString function should return native string for overridden…
5d35b6e 
… descriptor accessors` (close DevExpress#1713) (DevExpress#1714)
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked Issues that were automatically locked by the Lock bot label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@LavrovArtem LavrovArtem

Labels
!IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LavrovArtem