Delmaass/marketplace

[delmaass]

The goal of this PR is to fix every issues about marketplace and library, then to add a marketplace subscription system - a feature asked by the Biero association - which can have an impact on the price you pay a product in a marketplace.

Bug fixes

• Before the first activation of both library and marketplace, an error page was displayed when trying to access to one of this page as an administrator
• When a product had an infinite stock, its quantity was reduced in the back after an order. This led to troubles for future orders of this product
• A field required numberLeft positive whereas it could be negative because of infinite stock
• Marketplace and library were not destroyed when the association was destroyed, which could lead to troubles if the association name was used again
• Conflict when multiple associations had the same name (useful to fix it if we want different marketplace for a same association, now it can be biero, biero-1, etc.)

Subscription feature

A marketplace administrator can modify the subscriber status of an user. The new subscriber can then have prices advantages in the shop.

The subscriber status is indicated next to the user's balance.

The correct price is taken into account in the Transaction.

It is optional to add a subscriber price to a product.

[delmaass]

I don't understand why Django CI check is raising ERROR: associations.tests.event.test_calendar (unittest.loader._FailedTest) whereas I started this branch before the addition of the Calendar feature. Any ideas how to going through this test ?

[delmaass]

I also don't understand why npx prettier --write frontend works locally with successful checks npx prettier --check frontend with prettier@2.0.5 (the version used in the Git test) but the check fails...

[abocquet]

For the failing CI, try to merge master into your branch

[abocquet]

Hello, first of all thank you for you work , seems great! However your PR is pretty big (1000+ lines), so if you want to get relevant feedback, I suggest you split it up into smaller PRs. A simple way to do it is to open 1 PR by fixed issue you mention above :)