Code refactor

[Nishthajain7]

Contributor checklist

• This pull request is on a separate branch and not the main branch
• I have tested my code with the ./gradlew lintKotlin detekt test command as directed in the testing section of the contributing guide

---

Description

• Auto suggest UI is handled by SuggestionHelper
• Moved word suggestions to SugggestionHandler
• Created a separate helper for ConjugateHandler class

Related issue

• Code improvements to make Scribe ready for future features #426

[github-actions]

Thank you for the pull request! ❤️

The Scribe-Android team will do our best to address your contribution as soon as we can. If you're not already a member of our public Matrix community, please consider joining! We'd suggest that you use the Element client as well as Element X for a mobile app, and definitely join the General and Android rooms once you're in. Also consider attending our bi-weekly Saturday dev syncs. It'd be great to meet you 😊

[github-actions]

Maintainer Checklist

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 :)

• The linting, formatting and testing workflows within the PR checks do not indicate new errors in the files changed

  • Tests may need to be reran as they're at times not deterministic

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[Nishthajain7]

@andrewtavis Sorry for the delay. I completed this a few weeks ago and thought I made the PR but I realized I didn't. The GeneralKeyboard file still has ~1700 lines and I am sure it can be further improved. I'd like to know your suggestions on this. Thank you!

[andrewtavis]

Thanks so much for the PR, @Nishthajain7! We'll get to the review in the coming days :) :)

[andrewtavis]

Would you be able to check out the failing instrumentation tests though?

[Akshaykomar890]

Can I also take a look into why the instrumentation tests are failing? @andrewtavis

[andrewtavis]

Sure thing, @Akshaykomar890! Would appreciate your help with the review :)

[Akshaykomar890]

@andrewtavis @Nishthajain7

I fixed the failing instrumentation test! 🎉

Issue: The processSuggestions test was creating one SuggestionHandler instance but mocking a different one, so mocks never triggered.

Fix: Nishthajain7#1

Tested locally - test passes now
Build successful

@Nishthajain7 Once you merge my PR and update this branch, CI should pass! Let me know if you need anything 👍

[andrewtavis]

Thanks so much for the great collaboration, @Akshaykomar890! @Nishthajain7, would you want to merge in Nishthajain7#1 and then we can bring the changes here? From there we can work to bring this PR in? 😊

[Akshaykomar890]

Thanks, @andrewtavis 😊 That sounds great. Once @Nishthajain7 merges the fix, I’ll help verify that everything’s running fine so we can move this PR forward smoothly.

[angrezichatterbox]

I have added the commit here @Akshaykomar890

[angrezichatterbox]

I will try fixing the conflicts

[angrezichatterbox]

I will try fixing the errors later today