Sometimes a Purchase consists of multiple entries that need to be summed together. It would be nice to be able to just type it in and let it sum up automatically (or offer to use the sum as the price value).

Example:

Could have an extra multiline field where we just type numbers on each line and it sums them up

17.45
6.20
-------
23.65

The median can be interesting for some use cases, like having only two users over a longer period of time, but it is not very helpful for having many users over a short period of time (like a weekend trip).

Either add it next to the median or as an optional value that can be swapped by clicking the median.

It's good to track the real date of a purchase, but one may forget to add it directly after. It would be great to be able to specify the actual date of purchase then as compared to the date of data entry.

Example: Hotel is split evenly, as we can't give any of it back. But if some stays only 1 of 3 days it would be unfair to pay for the same amount e.g. for things like food, so we can assign weights for a Purchase for each member to split this more fairly.

This could also be used to model #63 by assigning a 0 weight or maybe removing the weight/unchecking it.

E.g. searching for "Groceries" could give us an idea then how much we've spent on that already

When a dialog is open e.g. to create a new Purchase hitting the back button on mobile will instead go to the previous route, should close the dialog instead (which is fullscreen anyway, so it's kind of expected).

https://dev.to/lilianaziolek/intercepting-back-button-on-mobile-in-vue-nuxt-vuetify-apps-222m

There should be a way to have a simple human- and machine-readable backup of all data around a Collective, preferrably as JSON. Django has a generic serializer that may help with that and there's also ways to aggregate related data as a whole https://cbuelter.wordpress.com/2016/10/26/collecting-related-objects-in-django/

This is a prerequisite before even thinking about opening this up to the public on a shared server.

Should not be cleared and remember values on next launch instead

• Allow to add paypal.me usernames to user-profiles
• In a step on the cash-up page, if the creditor has such a username in his profile, add a button that opens the www.paypal.me/<username>/<amount> in a new tab to give the debtor a quick way to pay back

In the bottom right corner on desktop

Maybe we should add formatting rules to this project for example: Black

Should only be visible when logged in

Try switching between Collectives by visiting different urls, sometimes we end up on the unknown page without any Collective links and the URL itself is also not correctly parsed, so there is no way to login

Demo: https://payshare.cbuelter.de/28d7c6ad-9548-45d6-b023-b8e3b0950a44

Take e.g. a shared flat: People come and go. A new flatmate should not be responsible for old purchases. Also we should not be forced to create a new Collective everytime the member number/constellation changes (which is currently pretty much the only effective way to deal with this).

This could probably be implemented by adding a join_date to each Membership and calculating each member's share of the Purchases/Liquidations starting from that date only, so that someone joining later will effectively have to pay only what he made use of.

This will make it easy to use the generator when needed, but we don't have to rely on avataaars.io being available, because it often is not. Instead download the result of the generator as an image and host it somehere and use the URL for the actual avatar.

The concept of a liquidation seems to be hard to grasp in some instances. It's kind of the opposite of how people seem to think about money and how one person is in debt to another.

We could possibly rephrase the whole concept in the frontend by swapping directions basically. Inside the dialog the 2nd option would then be "Add new Debt".

The https://getavataaars.com API is not very reliable and sometimes images are not served or only some of the partial SVGs. It would be nice to "save" the avatars and just serve them ourselves.

With a fresh setup of Python 3.7 and SQlite 3.29.0-1 testruns fail for some tests like:

self = <django.db.backends.sqlite3.base.SQLiteCursorWrapper object at 0x7fb4d359faf8>, query = 'INSERT INTO "purchases_membership" ("created_at", "modified_at", "member_id", "collective_id") VALUES (?, ?, ?, ?)'
params = ['2019-07-19 13:41:23.327457', '2019-07-19 13:41:23.327563', 1, 1]

    def execute(self, query, params=None):
        if params is None:
            return Database.Cursor.execute(self, query)
        query = self.convert_query(query)
>       return Database.Cursor.execute(self, query, params)
E       django.db.utils.OperationalError: no such table: main.purchases_collective__old

venv/lib/python3.7/site-packages/django/db/backends/sqlite3/base.py:303: OperationalError
________________________________________________________________________________________________ ERROR at setup of test_collective_purchases _________________________________________________________________________________________________

See:

• wagtail/wagtail#4941 (comment)
• https://code.djangoproject.com/ticket/29182

This should most likely be fixed by upgrading Django to 2.2+.
EDIT: Confirmed by @Zarathustra2 this seems to fix it.

It would be nice to mark a Collective as readonly so that no addition/modification can be done (UI should reflect that), but everything can still be viewed. We may be able to handle this in a generic way inside a middleware.

hello ,
error exec python manage.py createsuperuser
FROM python:3-slim-jessie

I need Help me plz ! :(

root@82eab9cc7148:/var/app# python manage.py createsuperuser
Username (leave blank to use 'root'): fbclol
Email address: [email protected]
Password:
Password (again):
Traceback (most recent call last):
File "manage.py", line 22, in
execute_from_command_line(sys.argv)
File "/usr/local/lib/python3.6/site-packages/django/core/management/init.py", line 371, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python3.6/site-packages/django/core/management/init.py", line 365, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 288, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/local/lib/python3.6/site-packages/django/contrib/auth/management/commands/createsuperuser.py", line 59, in execute
return super().execute(*args, **options)
File "/usr/local/lib/python3.6/site-packages/django/core/management/base.py", line 335, in execute
output = self.handle(*args, **options)
File "/usr/local/lib/python3.6/site-packages/django/contrib/auth/management/commands/createsuperuser.py", line 160, in handle
validate_password(password2, self.UserModel(**fake_user_data))
File "/usr/local/lib/python3.6/site-packages/django/contrib/auth/password_validation.py", line 44, in validate_password
password_validators = get_default_password_validators()
File "/usr/local/lib/python3.6/site-packages/django/contrib/auth/password_validation.py", line 19, in get_default_password_validators
return get_password_validators(settings.AUTH_PASSWORD_VALIDATORS)
File "/usr/local/lib/python3.6/site-packages/django/contrib/auth/password_validation.py", line 26, in get_password_validators
klass = import_string(validator['NAME'])
KeyError: 'NAME'

There are use cases for this I haven't thought of yet, e.g. things like yearly refunds (electricity) or changes in costs that have already been paid by everyone.

Use first_name in app instead since username must be unique.

After logging in the URL will e.g. look like host.com/transfers. This is not something that can easily be shared or bookmarked, as it contains no reference to the collective currently being logged in.

It would be nice to use host.com/collective-key/transfers instead.

It is currently quite annoying when switching between collectives, especially with using the app from a homescreen icon.

It would be nice to store tokens for all currently logged in collectives and allow for a quick change. One way to do that could be by scoping all localStorage values by collective id so that we can store as many as wanted next to each other.

Currently the order seems to be quite random and makes it hard to scan the list