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

current property conflicts with method current() #49

Closed
siritsch opened this issue May 25, 2015 · 4 comments
Closed

current property conflicts with method current() #49

siritsch opened this issue May 25, 2015 · 4 comments
Labels

Comments

@siritsch
Copy link

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()

@nomiero
Copy link
Contributor

nomiero commented May 27, 2015

There is no current() method in DocumentClient, do you mean the queryIterator returned by the query or readFeed method ?

@siritsch
Copy link
Author

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.

@nomiero
Copy link
Contributor

nomiero commented May 27, 2015

Makes sense, thanks for notifying us about the bug, we will get it fixed as soon as possible

@nomiero nomiero added the bug label May 27, 2015
shipunyc added a commit to shipunyc/azure-documentdb-node that referenced this issue Aug 15, 2015
- Implements name based routing
- Fixes bug Azure#49
@ghost
Copy link

ghost commented Aug 15, 2015

This has now been fixed.

@ghost 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
Labels
Projects
None yet
Development

No branches or pull requests

2 participants