Skip to content

NoMongo: Error occured while loading Pledges data #3869

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
gkbishnoi07 opened this issue Mar 21, 2025 · 21 comments
Open

NoMongo: Error occured while loading Pledges data #3869

gkbishnoi07 opened this issue Mar 21, 2025 · 21 comments
Assignees
Labels
bug Something isn't working MVP Needed for our 2025 MVP no-issue-activity No issue activity

Comments

@gkbishnoi07
Copy link

Describe the bug
The Pledges section fails to load due to issues with the GraphQL query. The error message indicates that the PledgeWhereInput and PledgeOrderByInput types are not recognized, and the field getPledgesByUserId is not found on the Query type. This suggests a mismatch between the frontend query and the backend schema.

To Reproduce
Steps to reproduce the behavior:

1.Open Talawa Admin (develop-postgres branch)
2. Login to the User Portal using [email protected].
3. Join an Organization & Visit an Organization Page
4. Navigate to My Pledges

Expected behavior
The pledges associated with the user should be fetched and displayed correctly.

Actual behavior
The page displays an error message:

  • "Unknown type 'PledgeWhereInput'. Did you mean 'MembersWhereInput'?"
  • "Unknown type 'PledgeOrderByInput'."
  • "Cannot query field 'getPledgesByUserId' on type 'Query'."

Screenshots

Image

Additional details

  • Verify that PledgeWhereInput and PledgeOrderByInput exist in the GraphQL schema (talawa-api).
  • Check if the getPledgesByUserId query and related types (PledgeWhereInput, PledgeOrderByInput) exist in the backend. If they exist, update the frontend to match; if not, add the necessary query and types in the backend.

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

@gurramkarthiknetha
Copy link
Contributor

@palisadoes please assign this issue

@mpdesai90
Copy link

Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

@mohyware
Copy link

@palisadoes Assign this issue to me

Copy link

github-actions bot commented Apr 2, 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 Apr 2, 2025
@palisadoes
Copy link
Contributor

Unassigning. Inactivity

@mohyware
Copy link

mohyware commented Apr 2, 2025

@palisadoes
I've made progress on this, but I got busy with other stuff this week. Can I submit a PR or get reassigned?

Image

@github-actions github-actions bot removed the no-issue-activity No issue activity label Apr 3, 2025
@mohyware
Copy link

mohyware commented Apr 5, 2025

Hello @palisadoes,

I have implemented the getPledgesByUserId query and all its related types in the backend. I have two questions:

  1. The users (pledgers) relation in Mongo is many-to-many, as seen here. so the frontend expects an array of users, but in the Postgres schema, it's many-to-one see here Should I update this?
  2. Should I write getPledgesByUserId tests in the fund one here or create a new dedicated one?

@palisadoes
Copy link
Contributor

  1. Use the existing Postgres API schema
  2. Your work needs to be applied to the develop-postgres branch with an API running the develop-postgres code.
  3. Write tests according to the standard in our documentation

@palisadoes
Copy link
Contributor

Your API PR was merged

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 Apr 18, 2025
@Cioppolo14 Cioppolo14 removed the no-issue-activity No issue activity label Apr 18, 2025
@palisadoes
Copy link
Contributor

Unassigned. Inactivity

@iamanishx
Copy link

@palisadoes is this needs to be completed before gsoc ? if no you can assign me

@hustlernik
Copy link
Contributor

hustlernik commented Apr 20, 2025

@palisadoes @Cioppolo14

May I take this up?

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 Apr 28, 2025
@Cioppolo14
Copy link
Contributor

Unassigning due to inactivity and/or no submitted PR. Others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue.

@hustlernik
Copy link
Contributor

@Cioppolo14 I have university exam going on, so need some time.

@github-actions github-actions bot removed the no-issue-activity No issue activity label Apr 29, 2025
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
@Cioppolo14 Cioppolo14 removed the no-issue-activity No issue activity label May 6, 2025
@Cioppolo14
Copy link
Contributor

@hustlernik I have reassigned you. Will you be able to get to it soon?

@hustlernik
Copy link
Contributor

@Cioppolo14 Yup, will try to complete this ASAP.

@palisadoes palisadoes added the MVP Needed for our 2025 MVP label May 19, 2025
@palisadoes
Copy link
Contributor

@hustlernik Are you still working on this?

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 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working MVP Needed for our 2025 MVP no-issue-activity No issue activity
Projects
Status: Backlog
Status: Backlog
Development

No branches or pull requests

9 participants