-
-
Notifications
You must be signed in to change notification settings - Fork 716
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
Implement sorting on the users screen #1074
Comments
@aashimawadhwa |
@chandel-aman Our policy is to assign no more than two issues to each contributor. 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. |
Thank you for the reminder. |
@aashimawadhwa Can you assign this issue to me? |
@kirtanchandak You already have 2 issues assigned to you on talawa-api. Please get the PRs merged before asking for more issues. As per the rules, you can only have 2 issues at once in your name. |
@noman2002 , I would like to work on this issue. Please assign me : ) |
@noman2002 , i would like to work on this issue , so please provide me more details about it and i have one doubt that to handle sorting first we need to implement the logic on api first then on frontend. |
@Prajwaldindokar5 Issues are assigned on first come first serve basis. |
ok , not a problem |
Describe the bug
Currently sorting is not implemented in the users screen, the aim is to implement the sort functionality with latest first, oldest first etc. options, you can refer from the posts screen.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
sorting of users on the basis of defined and selected attributes.
Additional details
NA
Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship PalisadoesFoundation/talawa#359
The text was updated successfully, but these errors were encountered: