Skip to content

API Extractor not able to parse "import * as __ from __" #9803

@marlass

Description

@marlass

Current solution for namespaces that we use relies on export * as grouping them.
Different solution is to rely on namespaces provided by TS.

The current solution makes it impossible to use API extractor for finding breaking changes in our API.

We can try if namespaces are usable solution for this case at all or we should completely drop namespacing actions/selectors and expose them directly.

To consider:

  • splitting namespaces in multiple files
  • refactoring (problems, ease of catching errors)
  • namespaces support by API extractor

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions