Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

[terra-application-v3] Enhance "active" state APIs for components that feature portaling #266

Open
tbiethman opened this issue Sep 2, 2021 · 0 comments

Comments

@tbiethman
Copy link
Contributor

tbiethman commented Sep 2, 2021

Story

Description

As a consumer, I would like to know when my component is present on the DOM ("active")

Motivation

So that I can accurate query the DOM for components that I render.

Definition of Done

We'll know we're done when we expose an API from portal-ed framework components that will tell consumers when they have reached the DOM.

Details

I have created a rough implementation of what I'd expect: terra-application-v2...application-v2-active-state-changes

Existing components that need (passive) changes:

  • Workspace
  • PrimaryNavigationLayout
  • Page

New components in V2V3 scope that will require similar implementations:

  • Modal
@tbiethman tbiethman added the Story label Sep 2, 2021
@tbiethman tbiethman added this to the Terra Application 2.0.0 milestone Sep 2, 2021
@neilpfeiffer neilpfeiffer changed the title [terra-application-v2] Enhance "active" state APIs for components that feature portaling [terra-application-v3] Enhance "active" state APIs for components that feature portaling May 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants