Fix the signature of class static fields as functions #2840
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.
Changes static fields that were defined as inline functions to avoid problems with some transpilers.
In components defined as classes, some static fields were defined as inline functions.
This PR changes those to plain functions in order to prevent a syntax error in transpilers that do not specify a default name for anonymous functions.
Published
victory@37.0.1-next.2
pre release packageWorking Codesandbox
Fix for #2839