Conversation
❌ Test ResultsStatus: Some tests failed! 🔍 Click to view failed testsTest Coverage ReportOverall Coverage Summary
Coverage by File/Directory
Coverage report generated at 2026-03-25T08:09:35.419Z |
melissag-ensemble
left a comment
There was a problem hiding this comment.
Currently, playground URLs are configured per block, allowing each code block to have a unique URL. Moving this to site-metadata would enforce a single URL across all blocks — is that an acceptable trade-off?
|
❌ Test ResultsStatus: Some tests failed! 🔍 Click to view failed testsTest Coverage ReportOverall Coverage Summary
Coverage by File/Directory
Coverage report generated at 2026-03-25T13:54:22.803Z |
hlx_statics/scripts/scripts.js
Outdated
|
|
||
| const hasCodePlayground = await hasCodePlaygroundJson(); | ||
| const codePlaygroundData = {}; | ||
| if (!hasCodePlayground) return; |
There was a problem hiding this comment.
This requires code-playground.json to exist before Prism will render any syntax-highlighted blocks (like codeblock and tab) - code-playground.json should only gate the playground button, not Prism itself.
melissag-ensemble
left a comment
There was a problem hiding this comment.
The playground URL is still coming from a central file (code-playground.json), so all blocks would share the same URL. The original per-block data-playground-url attributes allowed each code block to point to a different URL - I think that’s still the right approach.
❌ Test ResultsStatus: Some tests failed! 🔍 Click to view failed testsTest Coverage ReportOverall Coverage Summary
Coverage by File/Directory
Coverage report generated at 2026-03-26T10:22:48.375Z |
Description
Added metdata json for the code playground url
Issue
https://jira.corp.adobe.com/browse/DEVSITE-2304
Test URL
Previous : https://stage--adp-devsite-stage--adobedocs.aem.page/express/add-ons/docs/guides/learn/how-to/use-text
Update : https://codeplayground-metadata--adp-devsite-stage--adobedocs.aem.page/express/add-ons/docs/guides/learn/how-to/use-text