Skip to content
This repository was archived by the owner on Jul 31, 2023. It is now read-only.

Conversation

@mantljosh
Copy link

@mantljosh mantljosh commented May 10, 2023

The CodatLink component seems to not be consistent with whether the consumer is responsible for rendering the modal or if CodatLink is. In this sample, the consumer code has to create the container and position it in the center of the screen, however then the CodatLink component is attempting to be responsible for the width and the box shadows.

In our application we have a design system already in place for modals that renders a scrim, a box shadow, and is responsive with a max width of 480px. It will take up the full 480px if there is space. Below a certain width (i.e. mobile) we position and display our modal differently so it takes the full width.

IMO the CodatLink component needs to either be responsible for the entire "modal" aspect, or continue relying on the conumer placing it in a modal and no defining a fixed width (or if you have to define a fixed width for your content, removing the box shadow and centering the content should be suffcient)

image

@vercel
Copy link

vercel bot commented May 10, 2023

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

Name Status Preview Comments Updated (UTC)
link-sdk-sample-project ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 10, 2023 7:59pm

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant