I'm pretty new to TypeScript and I would like to know if there exists a good way to rewrite code to avoid TSLint error "object access via string literals is disallowed" in the following code
interface ECType
{
name: string;
type: string;
elementType?: string;
}
export var fields: { [structName: string]: Array<ECType>; } = { };
class ECStruct1 {
foo: string;
bar: number;
baz: boolean;
qux: number;
quux: number;
corge: ECStruct2[];
grault: ECStruct2;
constructor() {
...
}
}
fields['ECStruct1'] = [
{ name: 'foo', type: 'string' },
{ name: 'bar', type: 'int' },
{ name: 'baz', type: 'bool' },
{ name: 'qux', type: 'long' },
{ name: 'quux', type: 'ulong' },
{ name: 'corge', type: 'array', elementType: 'ECStruct2' },
{ name: 'grault', type: 'ECStruct2' }
];
Update: At the end the content above will be part of a self-generated file with more than 300 ECStruct
s, so I would like to have the class definition (e.g. ECStruct1
) followed by its meta-description (e.g. fields['ECStruct1']
).
You have a couple options here:
Just disable the rule
Use a variable instead of a string literal
Write/Generate an explicit interface
See MartylX's answer above. Essentially:
Any of these are reasonable solutions, although I'm not as much of a fan of #2 because it's mangling up your code for no good reason. If you're generating code anyways, perhaps generating a type for
fields
as in #3 is a good solution.A simple way is to define a variable to hold the value of ECStruct1:
and then, get access to the object by using the variable as index:
You can get rid of the rule. Look for
tslint.json
, the add a property"no-string-literal"
withfalse
, inrules
::What about this way? I don't know if you need the indexer (
[structName: string]: Array<ECType>;
) or not.Just use template literal annotation.
Probably not the best option, but using
works too