Summary
Follow up on the ergonomics of the requestModal.template option in Skybridge.
PR #586 added support for the optional template field in RequestModalOptions so Skybridge stays compatible with the Apps SDK API.
Open question
Today this looks like a low-level pass-through rather than a Skybridge-idiomatic API.
We should decide whether to:
- keep
template as a compatibility-only surface
- document the expected usage clearly
- introduce a higher-level Skybridge abstraction/helper for modal templates
Why
In review, Paul raised that it is unclear how users are expected to use this in practice:
- do they build a template from scratch?
- register it as a resource?
- then pass the value through?
That may be valid for Apps SDK compatibility, but the developer experience in Skybridge is still unclear and may need a follow-up design/doc pass.
Context
Summary
Follow up on the ergonomics of the
requestModal.templateoption in Skybridge.PR #586 added support for the optional
templatefield inRequestModalOptionsso Skybridge stays compatible with the Apps SDK API.Open question
Today this looks like a low-level pass-through rather than a Skybridge-idiomatic API.
We should decide whether to:
templateas a compatibility-only surfaceWhy
In review, Paul raised that it is unclear how users are expected to use this in practice:
That may be valid for Apps SDK compatibility, but the developer experience in Skybridge is still unclear and may need a follow-up design/doc pass.
Context