-
Notifications
You must be signed in to change notification settings - Fork 108
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
current property conflicts with method current() #49
Labels
Comments
There is no current() method in DocumentClient, do you mean the queryIterator returned by the query or readFeed method ? |
Sorry. I mean the current() method of QueryIterator. This class also has a property current, which stores the index of the current object in the resource array. |
Makes sense, thanks for notifying us about the bug, we will get it fixed as soon as possible |
shipunyc
added a commit
to shipunyc/azure-documentdb-node
that referenced
this issue
Aug 15, 2015
- Implements name based routing - Fixes bug Azure#49
Merged
This has now been fixed. |
ghost
closed this as completed
Aug 15, 2015
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is not possible to call the current() method of DocumentClient. If you try to do that an exception is thrown saying that current is not a method. The current () method should be renamed e.g. to currentElement()
The text was updated successfully, but these errors were encountered: