This looks odd to me
enum MessageStatusGroup {
PENDING = [1, 2, 3],
PUBLISHED = [4],
DRAFT = [0],
}
and my linter gives error
Is there any limitation in typescript that prevents specifing array as value?
-
This is not linter error, it’s compiler errorParzh– Parzh2023-01-13 08:45:59 +00:00Commented Jan 13, 2023 at 8:45
-
Please replace/supplement images of code/logs/errors with plaintext versions.jcalz– jcalz2023-01-13 15:21:11 +00:00Commented Jan 13, 2023 at 15:21
Add a comment
|
3 Answers
jna and TBA are right.
But may be you can simply workaround with :
export const MessageStatusGroup = {
PENDING : [1, 2, 3],
PUBLISHED : [4],
DRAFT : [0],
} as const;
It should do the trick. The 'as const' at the end will ensure immutability of MessageStatusGroup, then it can be used the same way as an enum.
Comments
Short answer is that TypeScript support numeric and string-based enums, array are not supported.
Comments
Yes, in TypeScript enums, the values must be either string or number types. An array is not a valid value. This is why your linter is giving an error.
TypeScript provides both numeric and string-based enums.
You can also point to other enums
enum Foo {
Bar = 'Baz'
}
enum PointTo {
Bar = Foo.Bar
}
And for numeric enums, you can also point to functions that return numeric values.
const numFunc = () => 4;
enum PointTo {
Function = numFunc()
}
Check out typescriptlang for more examples
