feat: implement safe area insets for Android and add development tooling #182
Merged
jose
merged 7 commits from android-safe-area-insets
into master
1 week ago
Loading…
Reference in new issue
There is no content yet.
Delete Branch 'android-safe-area-insets'
Deleting a branch is permanent. It CANNOT be undone. Continue?
Technical changes:
# Validate assets include safe area support
npm run assets:validate:android
```
This commentary doesn't seem to belong with "build" instructions. Things like "build:android:dev" are already in the build instructions. The "assets:validate:android" is new, so that's worth listing with all the other build commands, but it doesn't seem useful to other people to list all the work that has gone into fixing this problem.
1. Replace `env(safe-area-inset-*)` with the max() pattern
2. Test on all target platforms
3. Verify safe area behavior is consistent
This commentary especially seems only useful for historical purposes... not for building, and not even to help other people in the future unless it's for your own reference. If you want to keep this historical change log, let's make a folder under "doc"... something like "history" or "changelog", something that separates it from the documentation that will help future developers who don't need to know the whole history.
@trentlarson you're right: those weren't supposed to be there. I removed the misplaced documentation from BUILDING.md. (
validate:android
documentation was already included in a previous commit onmaster
.)"commitlint": {
"extends": [
"@commitlint/config-conventional"
]
The commitlint & husky pieces seem unrelated to this PR.
I reverted the changes to package.json; Cursor linted it and formatted + reordered some things around, but no actual changes were made to those packages. I made sure
capacitor-status-bar
was retained.👍
3969167d92
into master 1 week ago3969167d92
.