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

Accessing getters on EntityIterator directly sometimes buggy #1

Closed
Swader opened this issue May 18, 2015 · 0 comments
Closed

Accessing getters on EntityIterator directly sometimes buggy #1

Swader opened this issue May 18, 2015 · 0 comments
Assignees
Labels

Comments

@Swader
Copy link
Owner

Swader commented May 18, 2015

When accessing methods on the EntityIterator directly, one should always get the same results as if accessed directly on the first subelement of the Iterator. However, this was sometimes buggy - e.g. when properties were dynamically generated via certain methods. In such cases, methods should be tried first.

Offending code is __call and __get magic metods inside EntityIterator.

@Swader Swader added the bug label May 18, 2015
@Swader Swader self-assigned this May 18, 2015
@Swader Swader closed this as completed in 45cb6db May 20, 2015
Swader added a commit that referenced this issue May 20, 2015
Implemented Crawlbot, this closes #4 and closes #1
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

1 participant