Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Private Events #983

Closed
palisadoes opened this issue Sep 5, 2021 · 3 comments
Closed

Feature request: Private Events #983

palisadoes opened this issue Sep 5, 2021 · 3 comments
Labels
documentation Update documentation feature request unapproved Unapproved, needs to be triaged

Comments

@palisadoes
Copy link
Contributor

palisadoes commented Sep 5, 2021

Is your feature request related to a problem? Please describe.
The participants in all events are publicly visible to everyone. There needs to be options for more privacy.

Describe the solution you'd like

  1. The ability to make events private where only participants can see who is attending
  2. The optional ability to make private events invisible to persons not attending

Describe alternatives you've considered
N/A

Approach to be followed (optional)
N/A

Additional context
Tied to Issue PalisadoesFoundation/talawa-api#354

@github-actions github-actions bot added the unapproved Unapproved, needs to be triaged label Sep 5, 2021
@CyberWake CyberWake added documentation Update documentation enhancement and removed unapproved Unapproved, needs to be triaged labels Sep 10, 2021
@akshatgarg12
Copy link

@palisadoes There exists a property isPublic in event schema, should we use that to change the behaviour of the API.

@palisadoes
Copy link
Contributor Author

@palisadoes There exists a property isPublic in event schema, should we use that to change the behaviour of the API.

It should be. Please check with @sumitra19jha, @CyberWake and/or @utkarshshendge to be certain. They are all on our slack channel.

@github-actions
Copy link

github-actions bot commented Mar 4, 2022

This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

@github-actions github-actions bot added the no-issue-activity No issue activity label Mar 4, 2022
@palisadoes palisadoes added unapproved Unapproved, needs to be triaged and removed proposal labels Mar 4, 2022
@github-actions github-actions bot removed the no-issue-activity No issue activity label Feb 10, 2023
@noman2002 noman2002 closed this as not planned Won't fix, can't repro, duplicate, stale Feb 18, 2023
Ayush0Chaudhary pushed a commit to Ayush0Chaudhary/talawa that referenced this issue Mar 29, 2023
* added index.ts to vite.config.ts to ignore it recursively inside src directory

* removed index.spec.ts files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Update documentation feature request unapproved Unapproved, needs to be triaged
Projects
None yet
Development

No branches or pull requests

4 participants