Skip to content
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

bumped up flutter_reaction_button from 2.0.2 to 3.0.0+2. #2079

Merged
merged 15 commits into from
Nov 18, 2023
Merged

bumped up flutter_reaction_button from 2.0.2 to 3.0.0+2. #2079

merged 15 commits into from
Nov 18, 2023

Conversation

Azad99-9
Copy link
Contributor

@Azad99-9 Azad99-9 commented Oct 30, 2023

What kind of change does this PR introduce?

bug fix: bumped up flutter_reaction_button from 2.0.2 to 3.0.0+2.

Issue Number:

Fixes #2075

Did you add tests for your changes?

No

Snapshots/Videos:

If relevant, did you update the documentation?

Summary

Actually this #2075 issue required updation of all references of flutter_reaction_button package in the entire code base

Does this PR introduce a breaking change?

No

Other information

Have you read the contributing guide?

Yes

@github-actions
Copy link

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if either of these two conditions occur:

  1. The overall code coverage drops below the target threshold of the repository
  2. Any file in the pull request has code coverage levels below the repository threshold

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.

Reviewers

When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

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.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Congratulations on making your first PR! 🎊 If you haven't already, check out our Contributing Guidelines and PR Reporting Guidelines to ensure that you are following our guidelines for contributing and creating PR.

@palisadoes
Copy link
Contributor

Please fix the failing test

@Azad99-9
Copy link
Contributor Author

Please fix the failing test

files pubspec.yaml and pubspec.lock are listed in the unauthorized files.
In order to update the flutter_reaction_button package, editing of the files pubspec.yaml and pubspec.lock is required.

please have a look and help me with what can be done to pass the respective test.

@palisadoes
Copy link
Contributor

Please fix the failing test

files pubspec.yaml and pubspec.lock are listed in the unauthorized files. In order to update the flutter_reaction_button package, editing of the files pubspec.yaml and pubspec.lock is required.

please have a look and help me with what can be done to pass the respective test.

Accessing the authorized files is understood. You need to fix this error:

@Azad99-9
Copy link
Contributor Author

Please fix the failing test

files pubspec.yaml and pubspec.lock are listed in the unauthorized files. In order to update the flutter_reaction_button package, editing of the files pubspec.yaml and pubspec.lock is required.
please have a look and help me with what can be done to pass the respective test.

Accessing the authorized files is understood. You need to fix this error:

Yeah, understood.

@Ayush0Chaudhary
Copy link
Contributor

@Azad99-9 can you post video-rec of the reaction button?

Copy link
Contributor

@Ayush0Chaudhary Ayush0Chaudhary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't downgrade other packages.

pubspec.lock Show resolved Hide resolved
pubspec.lock Outdated Show resolved Hide resolved
pubspec.lock Outdated Show resolved Hide resolved
@Azad99-9
Copy link
Contributor Author

Azad99-9 commented Nov 5, 2023

@Azad99-9 can you post video-rec of the reaction button?

screen-20231105-182851.mp4

video of reaction button.

@palisadoes
Copy link
Contributor

Please fix the failing test

@Ayush0Chaudhary
Copy link
Contributor

Test are failing, fix them please!

@Azad99-9
Copy link
Contributor Author

Azad99-9 commented Nov 12, 2023

@palisadoes @Ayush0Chaudhary
I have worked on fixing the failing tests and i found out that, the test file that is failing has following lines of code:
await Hive.openBox<User>('currentUser');
await Hive.openBox<OrgInfo>('currentOrg');
await Hive.openBox('url');
these lines does not impact the actual test logic in that file : talawa/test/widget_tests/after_auth_screens/app_settings/app_setting_page_test.dart.

So i tried removing those lines and ran the tests and all the tests were passing.
Shall i commit the changes that were made to the test file.

@Ayush0Chaudhary
Copy link
Contributor

@palisadoes @Ayush0Chaudhary
I have worked on fixing the failing tests and i found out that, the test file that is failing has following lines of code:
await Hive.openBox<User>('currentUser');
await Hive.openBox<OrgInfo>('currentOrg');
await Hive.openBox('url');
these lines does not impact the actual test logic in that file : talawa/test/widget_tests/after_auth_screens/app_settings/app_setting_page_test.dart.

So i tried removing those lines and ran the tests and all the tests were passing.
Shall i commit the changes that were made to the test file.

Yes

Copy link

codecov bot commented Nov 14, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c2cfa97) 76.39% compared to head (d723800) 76.17%.
Report is 4 commits behind head on develop.

❗ Current head d723800 differs from pull request most recent head aa208d9. Consider uploading reports for the commit aa208d9 to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2079      +/-   ##
===========================================
- Coverage    76.39%   76.17%   -0.22%     
===========================================
  Files          152      152              
  Lines         7442     7442              
===========================================
- Hits          5685     5669      -16     
- Misses        1757     1773      +16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@noman2002
Copy link
Member

@Azad99-9 Please fix the conflicting files.

@Azad99-9
Copy link
Contributor Author

@noman2002 Please advise on resolving the 'unauthorized files' error.

@palisadoes
Copy link
Contributor

@noman2002 Please advise on resolving the 'unauthorized files' error.

The test is failing because you have edited one or more files that we more carefully track to reduce the risk of breaking our GitHub action workflows and other related automation. This is to be expected in certain types of PRs especially those that alter the packages required by the repo’s app.

@Azad99-9
Copy link
Contributor Author

Please fix the failing test

files pubspec.yaml and pubspec.lock are listed in the unauthorized files. In order to update the flutter_reaction_button package, editing of the files pubspec.yaml and pubspec.lock is required.

please have a look and help me with what can be done to pass the respective test.

@palisadoes please have a look at this.

Copy link
Member

@noman2002 noman2002 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@palisadoes palisadoes merged commit 4603ad1 into PalisadoesFoundation:develop Nov 18, 2023
5 of 6 checks passed
palisadoes pushed a commit to palisadoes/talawa that referenced this pull request Jan 10, 2024
…oundation#2079)

* bumped up flutter_reaction_button from 2.0.2 to 3.0.0+2.

* added required fields for the widget

* formatted firebase options

* upgraded the previously downgraded packages

* undoing build.gradle change

* fixed failing test

* increased codecoverage of multi_reaction.dart from 94% to 100% by writing additional tests.

* formatted the changes.

* resolved conflict code

* fixed failing tests

* fixed failing tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bump flutter_reaction_button from 2.0.2 to 3.0.0+2
4 participants