search

BreakOutEvent / breakout-backend

The backend for BreakOut
GNU Affero General Public License v3.0
12 stars 0 forks source link

The unregisteredSponsor has to be dominant #134

Closed kenodressel closed 8 years ago

kenodressel commented 8 years ago

When I am a participant and also a sponsor and create a new offline sponsoring for my team, I will be the sponsor although I entered unregisteredSponsor data. If unregisteredSponsor data is entered the backend should prefer this kind of data.

florianschmidt1994 commented 8 years ago

Do we want to handle this implicitly like you said it would it be reasonable to split this into multiple end points?

Gesendet von mobilem Gerät. Bin unterwegs.

Florian Schmidt +49 15753003770

On 19.05.2016, at 08:49, Keno Dressel notifications@github.com wrote:

When I am a participant and also a sponsor and create a new offline sponsoring for my team, I will be the sponsor although I entered unregisteredSponsor data. If unregisteredSponsor data is entered the backend should prefer this kind of data.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub

kenodressel commented 8 years ago

I think an implicit handling is enough for this season but we should probably split it into two endpoints for next year.

florianschmidt1994 commented 8 years ago

I assume the same rule should apply to challenges?

kenodressel commented 8 years ago

correct On May 19, 2016 17:33, "Florian Schmidt" notifications@github.com wrote:

I assume the same rule should apply to challenges?

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/BreakOutEvent/breakout-backend/issues/134#issuecomment-220362518