mirror of
https://github.com/fluencelabs/assemblyscript
synced 2025-04-25 15:12:12 +00:00
06f99406be
Starting with explicit loads and stores as part of the respective type namespaces. Might become handy for use with portable code, because these can be polyfilled, while load<T> and store<T> can't.
lint
Recommended TSLint rules for use with AssemblyScript. Meant to spot the most common issues as you type.
Not a sophisticated checker in its current state.
Usage
Add the following tslint.json to your project:
{
"extends": "@assemblyscript/lint"
}
Add additional rules if necessary.
Add a script to your package.json:
"scripts": {
"lint": "tslint -c tslint.json --project ./path/to[/tsconfig.json] --format as"
}
Now, to check your sources, run:
$> npm run lint
If you are using Visual Studio Code, there's also a TSLint extension that highlights issues as you type.
Custom rules
- as-types checks that all types are annotated or have an initializer.
- as-variables checks the use of
varandletto match their semantic meaning. For reference,varbecomes a distinct local or mutable global, whileletbecomes a shared local.