Skip to content

fix: inset compatibility #345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 7, 2022
Merged

fix: inset compatibility #345

merged 1 commit into from
Nov 7, 2022

Conversation

yuuk
Copy link
Contributor

@yuuk yuuk commented Nov 6, 2022

No description provided.

@vercel
Copy link

vercel bot commented Nov 6, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
drawer ✅ Ready (Inspect) Visit Preview Nov 6, 2022 at 3:19PM (UTC)

@codecov
Copy link

codecov bot commented Nov 6, 2022

Codecov Report

Merging #345 (ac700dc) into master (4209fae) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #345   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines          112       112           
  Branches        37        37           
=========================================
  Hits           112       112           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@afc163 afc163 merged commit 47d4eea into react-component:master Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants