-
Notifications
You must be signed in to change notification settings - Fork 95
Restructure code #176
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
Restructure code #176
Conversation
e5ed004 to
aef9d10
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like it!
Just one suggestion
🌮
98ebb38 to
5414d3c
Compare
c37ee08 to
ed86de1
Compare
5414d3c to
2b61652
Compare
2b61652 to
8f57cf0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM !
|
bors merge |
|
Build succeeded: |
Breaking change:
Index.create(...)a@classmethodinstead of a@staticmethod. Why? Put the logic related to an index in theIndexclass instead of theClientclass.See the difference between static and class methods in Python: https://stackabuse.com/pythons-classmethod-and-staticmethod-explained/.
Index.get_indexes(). Since it's not related to only one index, this method should not be present in theIndexclass.update()method returns anIndexobject instead of adictbecause it's more convenient to manipulate object instead of dict. This is consitent withclient.index('movies').fetch_info()andclient.create_index('movies)andclient.index('movies')Changes:
assert isinstance(response, Index)