Is your feature request related to a problem? Please describe.
Event organizer email should be added to contact organizer through email .
https://github.com/fossasia/open-event-attendee-android/issues/1964
Additional context
Event details already have relationship. Please check the model before opening issue.
Please mention the relationship used to get the organizer email and then close the issue
owner = db.relationship('User',
viewonly=True,
secondary='join(UsersEventsRoles, Role,'
' and_(Role.id == UsersEventsRoles.role_id, Role.name == "owner"))',
primaryjoin='UsersEventsRoles.event_id == Event.id',
secondaryjoin='User.id == UsersEventsRoles.user_id',
backref='owner_events',
uselist=False)
404 Not found
404 Not found
We are already doing many functions using organiser . Since its already related to User as defined in the model. I dont know about android client, but we are already performing operations using web client on organiser. So you are the boss here to decide @iamareebjamal , but we can't add every functionality in server just because the android client get fetch info easily.
Give me a link of organizer info of an event @kushthedude
Nobody is talking about android client, I'm asking the API link to fetch organizer email.
We are already doing many functions using organiser . Since its already related to User as defined in the model
I don't know what that means
I dont know about android client, but we are already performing operations using web client on organiser.
Who cares about web or android, both use the same server, so there must be same endpoint used by both
but we can't add every functionality in server just because the android client get fetch info easily.
It seems someone from Android hurt you, I don't know what this statement means. No one asked for fetching info easily of by chaining 20 API calls. If you have a link to API endpoint by which I can get the email of the organizer, then link it and close the issue. If not, it needs to be added
It seems someone from Android hurt you, I don't know what this statement means. No one asked for fetching info easily of by chaining 20 API calls. If you have a link to API endpoint by which I can get the email of the organizer, then link it and close the issue. If not, it needs to be added
I dont think why would you think if someone hurt me, Also FE does not make 20 api calls, if it was the case the following attribute have been added before. As I already said if you want to add let it be.
Who cares about web or android, both use the same server, so there must be same endpoint used by both
Since both use the same server, the things which FE is able to do should be the case with android. I think you like the android one's more than the web client.
That's why I am asking you to paste the link frontend uses to get the organizer info. I'll refrain from responding unless you have something productive to add to the discussion.
I would like to take up the issue and add organizer email in the event detail @prateekj117 @iamareebjamal
@akshat0047 Go ahead.
@akshat0047 @PARAG00991 actually I am working on this ....can you please take another issue.
@ranjsa Without claiming the issue? You always need to claim the issue before working on it.
@PARAG00991 yes sorry I forgot to add that . In the issue description
@ranjsa When did my username change from @prateekj117 to @PARAG00991? Ok no issue. You go ahead with this one.
@prateekj117 lol Actually it came in suggestions at top ...so I thought it was you ..... but thanks for correcting me and I am working on it .
@ranjsa are you still working on this?
@akshat0047 yes ...
It's been 16 days. You can work on it @akshat0047