-
-
Notifications
You must be signed in to change notification settings - Fork 494
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
Made the posts UI better #2218
Made the posts UI better #2218
Conversation
Our Pull Request Approval ProcessWe have these basic policies to make the approval process smoother for our volunteer team. Testing Your CodePlease make sure your code passes all tests. Our test code coverage system will fail if either of these two conditions occur:
The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing. ReviewersWhen your PR has been assigned reviewers contact them to get your code reviewed and approved via:
Reviewing Your CodeYour reviewer(s) will have the following roles:
Other🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #2218 +/- ##
===========================================
- Coverage 87.65% 82.34% -5.32%
===========================================
Files 155 151 -4
Lines 7356 7029 -327
===========================================
- Hits 6448 5788 -660
- Misses 908 1241 +333 ☔ View full report in Codecov by Sentry. |
@ShubhamTiwari55 The asset is not loading in the screenshot, how can we check the post design. please upload a proper image showing before and after. |
|
@ShubhamTiwari55 Alse attach a screenshot of before. |
@ShubhamTiwari55 Instead of just image. Use the same component used on home screen for posts. |
|
Okay, doing the required changes |
@noman2002 Is it okay now ? |
This is not the component used on home screen. It has comments, likes and etc. |
|
Yes, perfect now. Please write the tests for missing lines. |
@ShubhamTiwari55 Merge the latest code into this branch. |
@noman2002 I have merged it already. Kindly merge this PR as all changes have been done. |
], | ||
), | ||
), | ||
IndividualPostView(post: samplePost), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is still not covered. Connect with @Ayush0Chaudhary or @Dante291, anyone will help you out.
@Ayush0Chaudhary Can you please help me out in test part ? |
Hello @ShubhamTiwari55 hope you're doing well, ok so I checked out your commits and saw that in your test you've commented out the test for Testing for UI is basically different than Unit testing as you need to check whether the required widgets appear on the screen and is performing task properly or not, in your case all you had to do is check whether the Individual post widget is present in profile page view. You need to create the demo or mock Individual post widget in your test file and then create a test to check whether it shows up at the right section of the UI, that's it. If you still get stuck hit me up on slack or ask your query in Talawa-mobile channel. |
I have added the tests for IndividualPostView(post: samplePost), also but still the code coverage is not 100%. Here is the screenshot showing all tests passes for that test code also. Can you suggest me what should I add more in order to reach the coverage to 100% |
@ShubhamTiwari55 you're separately checking Individual post by directly rendering it by doing this |
@ShubhamTiwari55 for all the UI changes you have made in profile_page.dart please replicate them in demo_profile_page.dart also. |
@Azad99-9 I don't think that it would be required because @ShubhamTiwari55 is working on showing some sample post in the profile_page view but since demo_profile_page.dart file contains the view only for tutorial, there is no need to show any type of post in it? demo_profile_page_.dart file is only for the tour of the app before user join in any organization or log in, since no user is logged in then there is no need for any sample post to be displayed. |
@@ -28,6 +33,40 @@ class ProfilePage extends StatelessWidget { | |||
/// | |||
final MainScreenViewModel? homeModel; | |||
|
|||
/// a_line_ending_with_end_punctuation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Write a meaningful documentation here. Moreover, any mock data should be outside the component. If necessary, create a new file for this.
/// | ||
/// **returns**: | ||
/// None | ||
void main() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Documentation for main
function is not needed. Please remove.
class ProfilePage extends StatelessWidget { | ||
const ProfilePage({ | ||
ProfilePage({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove dummy data as suggested and mark this class as const again. Having const classes improves performance; we should not remove them unnecessarily.
@Dante291 yeah but already there are these hard coded images in demo_profile_page.dart which are being shown in previous format 'tile format' this may cause UI inconsistentcy. or else @ShubhamTiwari55 just please remove these hard coded images from demo_profile_page.dart. This way we can maintain Consistent UI. |
Dear @palisadoes, I hope this message finds you well. I wanted to inform you that due to my ongoing college end semester exams, I have been unable to dedicate the necessary time and focus to the issue associated with the Pull Request #2218 In light of this, and after discussing with @Dante291 on Slack, we believe that they have a better solution for the issue at hand. Therefore, I am closing the PR and unassigning myself from this particular issue. I have full confidence that @Dante291 will effectively handle and contribute to the resolution of this matter. I sincerely apologize for any inconvenience caused, and I appreciate the understanding and support from the team. As my exams are concluding, I look forward to resuming regular contributions to the organization. Once again, thank you to everyone for your valuable reviews and assistance. Best regards, |
What kind of change does this PR introduce?
Enhanced the UI of posts page by making it vertically scrollable.
Issue Number:
Fixes #2196
Did you add tests for your changes?
No
Snapshots/Videos:
If relevant, did you update the documentation?
No
Summary
I used listview to make the post page like a news feed which enhanced its UI and now it is looking better.
Does this PR introduce a breaking change?
No