fix(fela): get rid of const enum in typings #671
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently
fela
typings have a single use ofconst enum
and it means that you cannot to build a project with--isolatedModules
. See for more details: microsoft/fluent-ui-react#613Actually, this change is very important because
const enum
s are not supported by@babel/preset-typescript
, too.I added typings for
fela-utils
as this package contains constants that can be used by consumers.microsoft/TypeScript#20703 (comment)
Packages
fela
Versioning
Actually, it's a breaking change that requires a major bump because you will not able to use
TSubscribeMessageType
as value.Before
After
Checklist
Quality Assurance
yarn run format
)yarn run lint
)yarn run test
)yarn run flow
)