refactor: move all interactive keyboard code to dedicated interactive
folder (Android)
#353
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📜 Description
Move all interactive keyboard code to dedicated
interactive
folder/package in kotlin/Android.💡 Motivation and Context
Ideally in root android folder I'd like to keep a single
package
file and all other code should be placed in folders.Initially I created generic purpose folders, like
events
/listeners
/views
etc. However sometimes it may be hard to create generic purpose folders for specific files. Theoretically I could create folderscontrollers
/providers
, but they would contain only single files.So I took an inspiration from #346 PR, where I created
traversal
folder for keeping functionality related to view traversal/keyboard toolbar. And in this PR I moved all interactive-keyboard related code intointeractive
folder - it keeps file-system clean 😎📢 Changelog
CI
e2e
tests (Android);Android
interactive
folder;interpolators
folder tointeractive
;InteractiveKeyboardProvider
andKeyboardAnimationController
tointeractive
folder.🤔 How Has This Been Tested?
Tested on CI.
📸 Screenshots (if appropriate):
📝 Checklist