LG-4444: OverlayContext and useOverlay #2454
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 7d9d104 The changes in this PR will be included in the next version bump. This PR includes changesets to release 65 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
stephl3
force-pushed
the
steph/po-overlay-context
branch
from
d7e4f94
to
b02accb
Compare
|
Size Change: +1.58 kB (+0.12%) Total Size: 1.36 MB
ℹ️ View Unchanged
|
tsck
reviewed
Aug 12, 2024
packages/leafygreen-provider/src/OverlayContext/OverlayContext.tsx
Outdated
Show resolved
Hide resolved
packages/leafygreen-provider/src/OverlayContext/OverlayContext.tsx
Outdated
Show resolved
Hide resolved
packages/leafygreen-provider/src/OverlayContext/OverlayContext.spec.tsx
Outdated
Show resolved
Hide resolved
…der in LG provider
stephl3
force-pushed
the
steph/po-overlay-context
branch
from
4a310e8
to
7d9d104
Compare
tsck
approved these changes
Aug 13, 2024
stephl3
added a commit
that referenced
this pull request
Sep 3, 2024
* OverlayContext, useOverlayContext, and OverlayProvider * useOverlay to register, remove, and track isTopMostOverlay * Export overlay context related components and hooks and include provider in LG provider * README and changeset * Fix type and lint * Update registerOverlay logic and use more explicit generic type names
stephl3
added a commit
that referenced
this pull request
Sep 16, 2024
* OverlayContext, useOverlayContext, and OverlayProvider * useOverlay to register, remove, and track isTopMostOverlay * Export overlay context related components and hooks and include provider in LG provider * README and changeset * Fix type and lint * Update registerOverlay logic and use more explicit generic type names
stephl3
added a commit
that referenced
this pull request
Oct 10, 2024
* OverlayContext, useOverlayContext, and OverlayProvider * useOverlay to register, remove, and track isTopMostOverlay * Export overlay context related components and hooks and include provider in LG provider * README and changeset * Fix type and lint * Update registerOverlay logic and use more explicit generic type names
stephl3
added a commit
that referenced
this pull request
Oct 11, 2024
* OverlayContext, useOverlayContext, and OverlayProvider * useOverlay to register, remove, and track isTopMostOverlay * Export overlay context related components and hooks and include provider in LG provider * README and changeset * Fix type and lint * Update registerOverlay logic and use more explicit generic type names
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
✍️ Proposed changes
OverlayContext,OverlayProvider,useOverlayContext, anduseOverlayOverlayProviderinLeafyGreenProvider🎟 Jira ticket: LG-4444
✅ Checklist
For bug fixes, new features & breaking changes
yarn changesetand documented my changes🧪 How to test changes
Added unit tests