Skip to content

v1.0.6 — SKIE output as API contract

Latest
Latest

Choose a tag to compare

View all tags
@sorunokoe sorunokoe released this 13 May 08:26
v1.0.6
9f3ebd7

What's new

SKIE output as authoritative API contract

A real gap filled: the skill taught bridge patterns but said nothing about what happens when Kotlin API shifts underneath. Writing Swift against stale SKIE output produces non-compiling code with no obvious explanation.

references/architecture.md — new SKIE Output as API Contract section:

  • .swiftinterface inside the xcframework is the authoritative source for onEnum case names, type names, and nullability
  • Decision table: which Kotlin changes require rebuilding the xcframework before writing Swift (changes to @ObjCName-annotated API surface) vs. which don't (test sources, Android-only code, private members, body-only changes, Gradle files)
  • Best practice: read the relevant .swiftinterface before writing bridge code for a changed type

references/type-mapping.md — clarifying note in the onEnum(of:) section: case names are SKIE-generated output, not direct Kotlin names

SKILL.md — one new checklist item: xcframework must be rebuilt before writing Swift bridge code when the Kotlin API surface changed

Assets 2
Loading