Repository navigation
Ouro UI for Android v0.2.2
A pointer in a composed tree can no longer name an object's prototype, and every name a sender chooses must be the catalog's own. This follows core 0.18.2 (ourostack/ouro-ui-core#91).
- Pointers stay in the data:
validateTreerefuses a field'svalueor a bound input whose pointer has a segment__proto__,constructororprototype.setPointerwrites nothing through one.- The new
OuroComposed.isSafePointerandisDataPointersay whether a pointer is allowed. Kotlin's maps have no prototype, but Android refuses the same trees core does.
- Names are the catalog's own: a component, action or input field a sender names is taken only when the catalog itself has it, and a catalog may name only Ouro HX's own components. Android already worked this way; tests now pin it.
- A2UI streams: Android reads none, so core's checks on template paths and
updateDataModeldon't apply here. - Core 0.18.2: the pin moved from 0.18.1, by tag and SHA-256.
Checked on: CI only. The Robolectric tests run core's claims, the composed cases and the snapshots. The sample's X-ray and its composed card run on an Android 17 (API 37) emulator. The maintainer owns no Android device, so nothing here has run on real hardware yet. If you have a device and something differs, please open an issue.
Install: add maven { url = uri("https://ourostack.github.io/ouro-ui-android/maven") } to your repositories and implementation("bot.ouro.ui:ouro-hx:0.2.2"). The Maven files are also attached below.