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
Platonn
changed the title
Validate usability of TS namespaces on actions/selectors
API Extractor not able to parse "import * as __ from __"
Jul 20, 2021
btw. another problem with api-extractor ERROR: The expression contains an import() type, which is not yet supported by API Extractor: also seems to be solved in 7.18.0! See microsoft/rushstack#2140 (comment)
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:
The text was updated successfully, but these errors were encountered: