PalisadoesFoundation / talawa-admin

Admin portal for the Talawa Mobile App. Click on the link below to see our documentation
https://docs.talawa.io/
GNU General Public License v3.0
135 stars 543 forks source link

USER: Misplaced Screen Title & Fix Layout Structure #2071

Open GlenDsza opened 3 months ago

GlenDsza commented 3 months ago

Describe the bug In User Portal, across the screens, The title of the screen is placed in child container, resulting in empty space at top of all screen. Like Admin Portal, Screen Titles should be move from screen container to Parent Outlet Container.

To Reproduce Steps to reproduce the behavior:

  1. Login to User Portal
  2. Visit All screens and view empty space between title due to misplacement in screen container instead of Parent Outlet container.

Expected behavior All the Screen title's should be moved from individual screen container to parent outlet container.

Actual behavior Screen title's are placed in child screen container resulting in uneven look and empty space at top of screen.

Screenshots

image

image

Similarly for other screen as well.

GlenDsza commented 3 months ago

Pls Assign

dhanagopu commented 3 months ago

@GlenDsza 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, You have reached your limit, please wait until your existing issues are closed before requesting more issues.

anuragnegi000 commented 3 months ago

assign this issue to me

anuragnegi000 commented 2 months ago

sorry for the delay, i'm still working on it give me some more time please

anuragnegi000 commented 2 months ago

https://github.com/PalisadoesFoundation/talawa-admin/assets/115611556/9129af9c-50c3-41bd-8205-7eb4ff352a29

I have made changes within the child container itself without moving items from the child to the parent. The results are as expected. If any further changes are needed, please let me know. Otherwise, please grant me permission to raise a PR.

palisadoes commented 2 months ago
  1. This looks OK.
  2. You don't need to ask permission to raise a PR or create an issue.
github-actions[bot] commented 2 months ago

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.

anuragnegi000 commented 2 months ago

why why i'm getting these conflicts while re-setting up the project

palisadoes commented 1 month ago

Please ask our slack channel for assistance

AnshulKahar2729 commented 1 month ago

Is anurag still working on this?

anuragnegi000 commented 1 month ago

@AnshulKahar2729 yes

palisadoes commented 1 month ago

Are you still working on this?

anuragnegi000 commented 1 month ago

@palisadoes yes i am working on this

github-actions[bot] commented 1 month ago

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.

palisadoes commented 1 week ago

Unassigning inactivity

anuragnegi000 commented 1 week ago

I am working on it please assign me

github-actions[bot] commented 1 day ago

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.

palisadoes commented 22 hours ago

Unassigning. Inactivity