Skip to content

NoMongo: Add capacity field to Venue and create query to fetch by organizationId #3463

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

Open
Doraemon012 opened this issue Apr 28, 2025 · 3 comments
Labels
feature request MVP Needed for our 2025 MVP no-issue-activity No issue activity unapproved Unapproved for Pull Request

Comments

@Doraemon012
Copy link
Member

Is your feature request related to a problem? Please describe.

We need to update query and mutations according to the recently migrated develop-postgres branch of talawa-api. Currently, the capacity field is missing in Venues, and there is no query to fetch venues by organizationId.

Describe the solution you'd like

  • Add capacity field to the Venue model in the API.
  • Create a query to fetch venues by organizationId.

Describe alternatives you've considered

  • Filtering venues on the client side (inefficient).
  • Handling capacity separately (inconsistent).

Approach to be followed (optional)

  • Update models and migrations.
  • Add new queries/mutations in the API.
  • Update the schema accordingly.

Additional context

This is needed to fix the related Talawa-Admin issue #3554

Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship:
PalisadoesFoundation/talawa#359

Copy link

github-actions bot commented May 6, 2025

This issue did not get any activity in the past 10 days and will be closed in 180 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 May 6, 2025
@palisadoes
Copy link
Contributor

Unassigned. Abandoned

@github-actions github-actions bot removed the no-issue-activity No issue activity label May 19, 2025
@palisadoes palisadoes added the MVP Needed for our 2025 MVP label May 19, 2025
Copy link

This issue did not get any activity in the past 10 days and will be closed in 180 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 May 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request MVP Needed for our 2025 MVP no-issue-activity No issue activity unapproved Unapproved for Pull Request
Projects
Status: Backlog
Status: Backlog
Development

No branches or pull requests

2 participants