Prepare group menu for a11y

[Larisa-Staroverova]

No description provided.

[cypress]

---

Test summary

2 • 0 • 0 • 0 • 0

---

Run details

Project	spartacus
Status	Passed
Commit	3d6cdf1 ℹ️
Started	Jun 11, 2021 4:53 AM
Ended	Jun 11, 2021 4:54 AM
Duration	01:01 💡
OS	Linux Ubuntu - 18.04
Browser	Electron 89

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[github-actions]

Public API changes

✔️ Nothing changed in analyzed entry points.

⚠️ Some entry points are currently impossible to analyze.

Read more

• @spartacus/asm/core - ERROR: "import * as ___ from ___;" is not supported yet for local files.
• @spartacus/cart/saved-cart/core - ERROR: "import * as ___ from ___;" is not supported yet for local files.
• @spartacus/core - ERROR: "import * as ___ from ___;" is not supported yet for local files.
• @spartacus/organization/administration/core - ERROR: "import * as ___ from ___;" is not supported yet for local files.
• @spartacus/organization/order-approval - ERROR: "import * as ___ from ___;" is not supported yet for local files.
• @spartacus/product-configurator/rulebased - ERROR: "import * as ___ from ___;" is not supported yet for local files.
• @spartacus/storefinder/core - ERROR: "import * as ___ from ___;" is not supported yet for local files.
• @spartacus/storefront - ERROR: The expression contains an import() type, which is not yet supported by API Extractor:
• @spartacus/user/account/components - ERROR: The expression contains an import() type, which is not yet supported by API Extractor:
• @spartacus/user/profile/components - ERROR: The expression contains an import() type, which is not yet supported by API Extractor:

💰 How to debug problems?

Read more

Problem with import() type

It happens when type is deduced by TS based on code and at the same time the deduced type is not present in the file.
In this specific case to support api-extractor it's worth to add type declaration explicitly.

Debugging steps:

• go to the bot action logs
• find api-extractor logs for broken library
• check in which file and line the problems exists
• build the library locally and check content of the file mentioned in logs (look for import()
• add explicit type to problematic source code
• build the library once again and verify that the import( is no longer present
• commit and push the code with defined type

Problem with import * as ___

Api-extractor doesn't support this namespace syntax.
Check if you really need to use namespace in the library. Try to avoid namespaces when possible.