-
Notifications
You must be signed in to change notification settings - Fork 38
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
fix: Fix complex condition detekt errors #201
fix: Fix complex condition detekt errors #201
Conversation
Thank you for the pull request!The Scribe team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :) If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Android rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you! Maintainer checklist |
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.
Great PR @albendz. The changes look good to me. Thanks :)
Could we get the merge conflicts resolved and then I'll bring this in? Thanks so much to you both! |
I'll take a look at the merge conflicts |
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.
Appreciate the help with the merge conflicts, @albendz! Thanks for all your support to the project 😊
Contributor checklist
Description
Resolve complex condition errors for linting.
I tested this by running automated tests outside the project in my own scratch environment that made sure the before/after results of the boolean conditions were the same with and without my changes. I tried adding unit tests and started going really deep with mocking and hit some issues that didn't quite make sense when mocking in the MyKeyboardView constructor.
I'm not able to test the app on my device unfortunately. I've started a thread on Matrix for help.
Testing code
Related issue