Repository navigation
Conversation
6a0ce6c to
3aa2d91
Compare
|
馃悽 Performance warning. |
|
馃悽 Performance warning. |
Expose nextcloud-deck-board through an opt-in loading event so other Nextcloud apps can reuse the existing board and card detail components. Isolate embedded stores, routing and sessions without changing the host URL or global session headers. Preserve active cards when opening archived card details and keep undo actions bound to their board instance. Co-authored-by: Copilot <copilot@github.com> GPT-6.1 Sol Signed-off-by: Stefan Lender <Stefan.Lender@dataport.de>
3aa2d91 to
e470562
Compare
|
馃悽 Performance warning. |
|
Closing this PR because we have changed the approach in nextcloud/circles#3055 following review feedback. Instead of introducing a Deck-specific web component, Teams now uses Nextcloud鈥檚 existing Reference/Smart Picker widget API. This allows apps to provide embedded views through a shared interface rather than requiring a separate integration in Teams for each app. Deck already provides an interactive board widget, so the new web component is no longer required for this approach. |
Resolves:
nextcloud/circles#2948
Relates:
nextcloud/circles#3055
Summary
This pull request gives us the opportunity to use the deckboard in the Teams app via a web-component.
Expose nextcloud-deck-board through an opt-in loading event so other Nextcloud apps can reuse the existing board and card detail components. Isolate embedded stores, routing and sessions without changing the host URL or global session headers. Preserve active cards when opening archived card details and keep undo actions bound to their board instance.
TODO
Checklist
馃 AI (if applicable)