-
Notifications
You must be signed in to change notification settings - Fork 885
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix type errors in i18n #3027
Comments
The issue here seems to be just a case of bad typing. In this particular file the context has 3 values: export interface ListrContext {
config?: I18nConfig;
reporter: ErrorReporter;
messages: Map<string, { message: string }>;
} setting the type of the context for each of the helper functions and the list itself should resolve this issue: e.g. const list = new Listr<ListrContext>( return configPaths.map((configPath) => ({
task: async (context: ListrContext) => {
try { |
Also, when fixing it, I found that the error instance is split into several lines, which is not allowed for Error. parser.SyntaxError itself is not callable, it is just described by the Error interface.
But a question: Where can I create a class node_modules\intl-messageformat-parser |
Yes, but a few comments:
|
Which file is this in? |
Hmm, I see your point. Looks like each of these errors have to be handled separately.
|
Task for #1660
(inherited from previous project)
The text was updated successfully, but these errors were encountered: