splitwise
splitwise copied to clipboard
Python SDK for Splitwise
Hello, We are trying to add an inconstant number of ExpenseUser according to the number of key:values in the previously created **usersInfo** dictionary, something like this: `{'349': '1,34', '396': '0,00',...
getExpenses Call can also accept a visible argument that controls if the response contains deleted expenses
The `User` class overrides `__getattr__` to return `None` ([link](https://github.com/namaggarwal/splitwise/blob/master/splitwise/user.py#L126)). I am not sure why this is, but a side effect is that when you check for the existence of magic...
Fixes #62 https://dev.splitwise.com/#tag/expenses/paths/~1get_expenses/get is a bit silly, as the param is friend_id but the JSON response is friendship id
According to API ref v.3.0 the correct parameter should be "friend_id", friendship_id is then returned for getExpense. Patch below: **./splitwise/__init__.py** ``` 460c460 < friendship_id=None, --- > friend_id=None, 471,472c471,472 < group_id(long,...
Fixes #66 Probably want to squash merge this.
Two minor copy/paste errors in test case naming.
https://dev.splitwise.com/#tag/notifications ``` { "notifications": [ { "id": 32514315, "type": 0, "created_at": "2019-08-24T14:15:22Z", "created_by": 2, "source": { "type": "Expense", "id": 865077, "url": "string" }, "image_url": "https://s3.amazonaws.com/splitwise/uploads/notifications/v2/0-venmo.png", "image_shape": "square", "content": "You paid...
The default installation `pip install splitwise` does not pick up on this new functionality, leading to problems and confusion
This adds basic but tested support for updateExpense and undeleteExpense methods.