-
-
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
Fixes MVP - Talawa #2108 #2114
Fixes MVP - Talawa #2108 #2114
Conversation
…into overflowError
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 #2114 +/- ##
===========================================
+ Coverage 79.85% 79.90% +0.05%
===========================================
Files 152 149 -3
Lines 7456 6973 -483
===========================================
- Hits 5954 5572 -382
+ Misses 1502 1401 -101 ☔ View full report in Codecov by Sentry. |
c37e036
to
b48e73d
Compare
@Ayush0Chaudhary Can you once check if thats all I am required to comment out? Few Extra changes involves Writing documentations and tests |
We can use QR to produce link that lead to our playstore app. What do you think @noman2002 ? |
@Ayush0Chaudhary Yes we can do that but currently we don't have it on playstore. |
Hey @noman2002 @Ayush0Chaudhary , If my opinion is welcomed, I would like to also propose that , Provided we don't have Playstore link., for the time being we can use our github releases link. Also we enable invite feature to invite people through social media but rather than using dynamic linking , we craft a message like I think it would be a good alternative for the time being. |
We won't have an App Store presence for the MVP. We don't have a strategy on how to handle incompatibilities between different versions of the mobile app, API and Admin. We'll need one by the middle of next year. It's best to have a link to the repo. @DMills27 is working on creating an issue that would help finalize where that location would be. For the purposes of the MVP I'd comment out the QR code code and then reinsert it when we have the definitive link. It'll probably change with each release prior to having an app store presence. Is there a way to embed a QR code in the repo so that people download the latest to their phone? |
https://github.com/PalisadoesFoundation/talawa/releases/download/automated/app-release.apk @palisadoes if we create a QR for this link. It will automatically download the latest build to their mobile phones. |
Thanks. I meant could we also embed it in a markdown file on GitHub to make it easier for the development community? README.md for example, but do so in an automated way so that the QR code in the master branch and develop branches download the appropriate APK. |
I think we can do that by creating two readme files for each branch. Creating a single Readme file and adding a placeholder is mentioned in this issue which is basically seems like not implemented as of now. I think best approach would be to create two readme.md for each branch...... Also what does this mean about this PR? Is it alright? |
@AyushRaghuvanshi Keep the QR code. Link to the APK in a way that matches the correct branch, if that is possible. If it's manual, then the resulting test should verify the branch is correct. Let us know when that is complete so we can give it a final review before merging. Is there anything in these files that need to be updated because of the disabled code?
|
@AyushRaghuvanshi have you commented out any unused packages in |
@Ayush0Chaudhary @noman2002 Don't merge this yet. I am still working on the changes @palisadoes recommended. |
@AyushRaghuvanshi What are the updates on this one? We need to merge this. |
@noman2002 I have made the package version changes. I was researching a lot if i can automate a process where we get QR code according to the branch. I think we can set up a .env file as well? and in the installation.md we state that to access QR code you need to add the correct branch release link @palisadoes How does that sound? |
@AyushRaghuvanshi I don't think it will work. It will make things more complex. I suggest we can just redirect the qr to master branch. There no need to redirect it to develop branch. |
The QR code should be for the |
fb9a716
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.
Looks good to me.
@Ayush0Chaudhary Please have a look.
@AyushRaghuvanshi What version of the API were you using to test against? What commit were you working with? @Ayush0Chaudhary is working on the |
@palisadoes I have the latest pull of the talawa-api repo. |
Thanks @AyushRaghuvanshi . Are you also up to date with all merged PRs, especially this one? @kb-0311 @Ayush0Chaudhary This may greatly assist your cross repo MVP goal and the eventual compatibility check. |
@palisadoes I wasn't. But Now I am with my latest push. |
Please fix the failing tests. |
@noman2002 @Ayush0Chaudhary Please review and merge if OK. |
2f271ac
into
PalisadoesFoundation:develop
* Fix:Overflow Error on PostWideget * Remove:Unused Hive Boxes * Fix:Responsiveness on Icons * Removed:dynamic Linking * Fix:Not Changing unauthorized files * Added:Documentation * Removed: Empty test * Modified:Test File name * Add:Tests for misses * Revert: removal of qr code * Fix:Splash bug * Fix:Format * Fix:Failing test
What kind of change does this PR introduce?
This PR removes all usage of dyanmic linking. Including Sharing Links and creating QR
Issue Number:
Fixes #2108
Did you add tests for your changes?
No, It wasn't relevant.
Summary
#2108 asks to remove three features to make app MVP ready. upon discussion with @Ayush0Chaudhary it was come to conclusion that Chat and notification is already removed.
Hence this PR removes dynamic Linking as well
Does this PR introduce a breaking change?
No
Have you read the contributing guide?
Yes