refactor: move KeyboardProvider props in separate file#1255
Merged
kirillzyusko merged 1 commit intomainfrom Dec 22, 2025
Merged
refactor: move KeyboardProvider props in separate file#1255kirillzyusko merged 1 commit intomainfrom
KeyboardProvider props in separate file#1255kirillzyusko merged 1 commit intomainfrom
Conversation
Contributor
📊 Package size report
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Moved props declaration to a separate file.
💡 Motivation and Context
Web implementation for
KeyboardProviderwill have a separate implementation and we need to re-use types, so in this PR I'm moving types into separate file to make it reusable.📢 Changelog
JS
KeyboardProviderPropsintypes/provider.tsfile;🤔 How Has This Been Tested?
Tested via CI (this PR);
📸 Screenshots (if appropriate):
📝 Checklist