User should not be able to join the beacon he/she is already part of.

[Aadeesh11]

User should not be able to join the beacon he is already part of (i.e., either he is a leader or follower). As all the beacons he is a part of are displayed under your beacons and can be navigated from there.
Secondly, when the beacon's details are fetched using query beacon(...) leader's name is returned as null, because of which Anonymous is getting displayed.

Originally posted by @nb9960 in CCExtractor/beacon#48 (comment)

[aadibajpai]

this shouldn't be possible already https://github.com/CCExtractor/beacon-backend/blob/master/graphql/resolvers.js#L120

[Aadeesh11]

this shouldn't be possible already https://github.com/CCExtractor/beacon-backend/blob/master/graphql/resolvers.js#L120

If the user(who created the beacon) is the leader himself, in that case user can join the beacon.

[aadibajpai]

this shouldn't be possible already https://github.com/CCExtractor/beacon-backend/blob/master/graphql/resolvers.js#L120

If the user(who created the beacon) is the leader himself, in that case user can join the beacon.

that is also a remnant of testing, so that a single user can test a beacon out by trying to join it after creating it. Should be easy to remedy. Might be worth to only do it when not running application in development so that it is still possible to test like that

[Aadeesh11]

Ok, understood.