You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## 📜 Description
Added `KeyboardController.state()` method.
## 💡 Motivation and Context
To achieve a parity with `Keyboard` API from `react-native` I decided to
add `KeyboardController.state()` method. By design it should act as
`Keyboard.metrics()` method. The reason why I choose `state` name
instead of `metrics` is because our data structure returns more like
state rather than a metrics - instead of `height` and layout information
we also return additional data, such as `duration` of last animation,
`timestamp` when last open happened, `target` of focused input and in
future potentially `type`, `appearance` and maybe other properties.
## 📢 Changelog
<!-- High level overview of important changes -->
<!-- For example: fixed status bar manipulation; added new types
declarations; -->
<!-- If your changes don't affect one of platform/language below - then
remove this platform/language -->
### JS
- added `KeyboardController.state()` method;
### Docs
- added a reference about `KeyboardController.state()` method;
## 🤔 How Has This Been Tested?
Tested manually in example app.
## 📸 Screenshots (if appropriate):
<img width="898" alt="image"
src="https://github.com/user-attachments/assets/338b6d9d-e82a-4f69-a023-01a1f41c1d20">
## 📝 Checklist
- [x] CI successfully passed
- [x] I added new mocks and corresponding unit-tests if library API was
changed
0 commit comments