authorizationAdvice — @gj-kit/expo-workouts
@gj-kit/expo-workouts/core에서 공개하는 function입니다. package version 0.1.1의 release declaration을 그대로 표시합니다.
검증된 import 예제
섹션 제목: “검증된 import 예제”import { authorizationAdvice } from '@gj-kit/expo-workouts/core';시그니처, 매개변수, 반환 타입
섹션 제목: “시그니처, 매개변수, 반환 타입”/** * Our opinion about what a settings screen should render, as a PURE function rather than a field on * `AuthorizationState`: if the platform's permission UI changes, an opinion baked into the contract * would be wrong in a way the raw facts would not have been. Adopt it or re-implement it. * * The one rule that matters: `'unknown'` NEVER produces `'openSettings'`. Every iOS read scope is * permanently `'unknown'`, so treating it as a problem would show every iOS user "go check * Settings" forever. */declare function authorizationAdvice(facts: AuthorizationFacts): AuthorizationAdvice;이 선언은 매개변수, optionality, 제네릭, 반환값, 공개 union/type 계약의 정본입니다. 호출 전 필요한 환경·권한·오류 경계는 패키지 Golden path와 이 subpath의 import 조건을 함께 확인하세요.
Release context
섹션 제목: “Release context”- 패키지:
@gj-kit/expo-workouts - 버전:
0.1.1 - 공개 entry:
./core - 소스: GitHub
구현 주석
섹션 제목: “구현 주석”Our opinion about what a settings screen should render, as a PURE function rather than a field on
AuthorizationState: if the platform’s permission UI changes, an opinion baked into the contract
would be wrong in a way the raw facts would not have been. Adopt it or re-implement it.
The one rule that matters: 'unknown' NEVER produces 'openSettings'. Every iOS read scope is
permanently 'unknown', so treating it as a problem would show every iOS user “go check
Settings” forever.