Open Azad99-9 opened 6 months ago
I would like to work on it .
Assign me this issue please
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.
Hey @AVtheking any update on this?
Hi @Azad99-9 was busy due to my exams.. will start working on it from tomorrow.
Unassigning myself busy in some other issue.
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.
I would like to work on this issue
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.
Working on it
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.
I am unassigning myself from my due to being occupied with other commitments.
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.
Can I be assigned this issue?
Working on it might take a few days..
I've fixed case 1. Would you prefer I submit a PR for this now, or should I complete the fixes for the other two cases first and then make a single PR?
please do everything in a single PR and share a video of it too.
@Azad99-9 I am not sure but this issue might be an internal error with Apollo Server (https://github.com/apollographql/apollo-client/issues/8898). I'm seeing the same problem when fetching members via the organization query. It seems like a broader issue with how certain queries are handled. Also on console logging the organization, it shows all the accurate data. Could we look into this? @palisadoes
@Azad99-9 @palisadoes Should I raise a PR for case 1 of this issue?
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.
@varshith257 Should I go ahead and raise a PR for the fixes so far? I'm still working on the other two cases but wanted to check in.
If you think needed multiple prs, go ahead
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.
Describe the bug before testing set org's
userRegistrationRequired: true
.Three cases of unexpected behaviour related to membershipRequests
case 1. Everytime register with a fresh account, new
membershipRequest
is being added to org's membershipRequests field but not to user's membershipRequests field.case 2. Even if the requests are being added to the org's membershipRequests field but they are not fetchable in the org's query.
case 3. As soon as we send a request through the sendMembershipRequest mutation all the previously added requests are also now fetchable.
To Reproduce Steps to reproduce the behavior:
Case 1:
case 1.webm
Case 2:
organizations
query. you will notice a mismatch of number of requests.https://github.com/PalisadoesFoundation/talawa-api/assets/120930148/161d1161-e841-47f2-a722-fcaf96b6a737
Remember this org to reproduce case 3.
Case 3:
organizations
query. you will notice the mismatch of number of requests disappears.https://github.com/PalisadoesFoundation/talawa-api/assets/120930148/961e8ca9-d89e-4da9-8e1a-156200b8b1bd
Additional details Add any other context or screenshots about the feature request here.
Potential internship candidates Please read this if you are planning to apply for a Palisadoes Foundation internship https://github.com/PalisadoesFoundation/talawa/issues/359