Repository navigation
First stable release: the public API (Annotate.install, AnnotateOptions, AnnotateBridge, the CLI
commands and the session bundle described in SCHEMA.md) now follows Semantic Versioning.
SwiftPM requirements written as from: "0.x" stop below 1.0; change them to from: "1.0.0".
Added
- React Native and Expo apps (iOS only). The
annotate-iosnpm package now ships an
AnnotateKit.podspecthat React Native / Expo autolinking picks up, and an Expo config plugin
("plugins": ["annotate-ios"]) that adds the install call to the AppDelegate (Swift or Obj-C).
The pod compiles AnnotateCore and AnnotateKit into oneAnnotateKitmodule, so AnnotateKit's
import AnnotateCorelines are now behind#if canImport(AnnotateCore). AnnotateBridge.install(file:)for Objective-C AppDelegates:
[AnnotateBridge installWithFile:@__FILE__];.AppInfo.frameworkin session.json (react-native·expo, absent for native apps), detected
at runtime; the prompt then tells the agent to edit the JS/TS components.- Pins on React Native views report the JSX component (
Text,View,TextInput…) as
typeName, for both the new and the old architecture; RN root, surface and react-native-screens
wrappers are skipped like UIKit plumbing.
Fixed
- An unlabeled switch was named by its state: the comment card quoted "1" and the screen outline
listed it as text "1". A toggle's value is no longer used as its text.
Changed
- Without a
.git, the project root is the folder withpackage.jsonone or two levels above the
Xcode project, so a React Native app's sessions land next to its JS source, not inios/. - The device mirror recognises Expo apps from
app.json/app.config.json
(ios.bundleIdentifier), so a cloud-built development build with no localios/folder isn't
polled on the slow schedule. - The npm package no longer restricts installs to macOS (
os), sonpm ciworks on Linux CI for
apps that depend on it; theannotatelauncher says it needs macOS instead.