Skip to content
This repository has been archived by the owner on Jan 16, 2023. It is now read-only.

Third Party Libraries

Alex Wilson edited this page Apr 22, 2020 · 8 revisions

Proposed Design:

Add new param to aemMetadata decorator: libs

  • libs param accepts an array of strings which represent paths in AEM
  • This array of strings is used to fetch HTML/CSS/JS from AEM

Scan all HTL files for inclusion

  • Look for data-sly-use, data-sly-resource, data-sly-include, etc
  • Build a list of all files that cannot be found in the user’s codebase
  • Loop through list and get all HTML/CSS/JS from AEM
  • This must be done recursively against all files retrieved from AEM - e.g. includes of includes
  • For all data-sly-use instances, we must add a model
  • This should be part of the CLI
  • These files need to be cached - perhaps .storybook/.libs
  • Perhaps it’s possible to update the component inclusion to be based on paths instead of types?

Usage

// .storybook/preview.js
addDecorator(aemMetadata({
  libs: [
    ‘/apps/core/wcm/components/’
  ]
});

TODO

Data Mapping using the generic model and potentially information from the dialog xml combined with the infinity json - this solution would only provide a partial mapping and additional mapping may have to be handled by the user

Clone this wiki locally