You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My understanding (and please let me know if I'm mistaken!) was that the <Variant /> tag needs to use the repeat=x system because in MDX v1 it's not possible to have constructs like this:
Making sweeping changes to the structure or content of these blocks can be hard because you have to keep track of and update all the repeat counts. Being able to mark the start and end of <Variant> ... </Variant> blocks using interleaved JSX would make it a lot easier to maintain the docs.
I believe we would need to update Gatsby to v5 and some other dependencies. We haven't gotten around to that yet and are currently busy with a few things right now. Hopefully soon!
Hi @timkim! I was just circling back on the DEVSITE-586 ticket and noticed it was closed as fixed. Does that mean the wrapper style Variant block is available for use in a current/future release? Our team would really love to have this feature to help with easier doc writing and maintenance
🙋 Feature Request
Hi Adobe I/O team, I wanted to request adoption of MDX v2 in order to enable interleaving of JSX and markdown, as solved in mdx-js/mdx#1039.
🤔 Expected Behavior
My understanding (and please let me know if I'm mistaken!) was that the
<Variant />
tag needs to use therepeat=x
system because in MDX v1 it's not possible to have constructs like this:😯 Current Behavior
And instead currently require this:
Which can be quite cumbersome to keep track of and update, especially when making a lot of structural/content changes across a documentation repo.
Potentially related, I found this known limitation of MDX v1:
aio-theme/packages/gatsby-theme-aio/src/components/MDXFilter/index.js
Line 69 in a2bdb52
💁 Possible Solution
Adopting changes from #1383 (not sure what other changes/testing would be required).
🔦 Context
In the Adobe Experience Platform Mobile SDK docs using Adobe I/O, we use a lot of code tabs to show snippets and examples, and each of those tabs use
<Variant>
blocks to show the tab content: https://developer.adobe.com/client-sdks/documentation/consent-for-edge-network/api-reference/#registerextensionMaking sweeping changes to the structure or content of these blocks can be hard because you have to keep track of and update all the repeat counts. Being able to mark the start and end of
<Variant> ... </Variant>
blocks using interleaved JSX would make it a lot easier to maintain the docs.💻 Examples
https://github.com/AdobeDocs/aep-mobile-sdkdocs
🧢 Your Company/Team
Adobe/Experience Platform Mobile SDK
🎁 Tracking Ticket (optional)
The text was updated successfully, but these errors were encountered: