Update docs on Events end point to accomodate additional fields for Front end's sidebar

[abhinavk96]

The frontend facilitates all the public aspects of an event through a side menu as shown below.

However, it is desired to only show a menu item, if it's corresponding entries exist. For instance, display the item sessions, if sessions are present, display speakers if speakers are present. Display schedule if the schedule is published etc.

To achieve this functionality the frontend has to make a call to the corresponding endpoint to check if sessions or speakers exist, but that results in sending 100s of network requests for data, user is probably not going to view anyway.

Thus there needs to be an api endpoint or property values in the event schema itself, which tells if sessions, speakers are present for a given event. Current production environment has revealed that querying sessions and speakers results in a significant overhead.

[abhinavk96]

@iamareebjamal What would be the correct approach to rectify this situation.

[iamareebjamal]

An event info endpoint which tells the status and information about what is present in the event in form of booleans

[apoorvkhare07]

Is this issue up for taking ?
Would like to work on it.

[abhinavk96]

@apoorvkhare07 go ahead.

[abhinavk96]

@apoorvkhare07 I have added the fileds in #5560
As a beginner's issue perhaps you can instead help with updating the docs corresponding to this change. I have modified the issue title.

[iamareebjamal]

@CosmicCoder96 This will slow down the list queries by a lot. This should be handled by a separate relationship to event

[abhinavk96]

@iamareebjamal okay, will make a new PR.

[prateekj117]

@iamareebjamal @CosmicCoder96 May I work on this issue?

[iamareebjamal]

Go ahead