How to migrate use of LegacyCard.Section?

[bjester]

I looked through the version 10 to 11 migration guide for the Polaris package, as well as the component documentation, and it isn't clear to me how to migrate to the new Card component for past usage of Card.Section structures?

For example, this taken from the documentation for what is now LegacyCard:

    <LegacyCard title="Customer">
      <LegacyCard.Section>
        <p>John Smith</p>
      </LegacyCard.Section>
      <LegacyCard.Section title="Addresses">
        <LegacyCard.Subsection>
          123 First St
          <br />
          Somewhere
          <br />
          The Universe
        </LegacyCard.Subsection>
      </LegacyCard.Section>
    </LegacyCard>

[akospaska]

I am faced with the same issue ... :-(

[kyledurand]

Every card is purely composable now to allow builders to be more creative. The idea is that you use the Box component along with layout components like BlockStack / InlineStack to create layout within the card so there's no one way to migrate that we can document.

There are plenty of examples of how we use the new Card

Here's a sandbox that closely matches the example you have above.

I'm closing this discussion for now. In the future please create issues over discussions for this sort of thing

[bjester]

In the future please create issues over discussions for this sort of thing

I asked a question. In the future, update those guidelines or disable discussions if you don't want questions here.

there's no one way to migrate that we can document.

Oh I see, and that's a good reason to not document at least one way in your migration guide. You're really inspiring people to use Polaris.

[akospaska]

In the documentation by the layout section the example code still uses a LegacyCard.Section.

When do you planning to update the documentation?

https://polaris.shopify.com/components/layout-and-structure/layout?example=layout-three-columns-with-equal-width

[kyledurand]

@bjester this feels like more of an issue with documentation than a question about the system.

@akospaska our team doesn't have the bandwidth to spend time on docs at the moment. I've added an issue to our backlog