aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_editor/src/test_utils.rs
diff options
context:
space:
mode:
authorbors[bot] <bors[bot]@users.noreply.github.com>2018-10-08 20:39:52 +0100
committerbors[bot] <bors[bot]@users.noreply.github.com>2018-10-08 20:39:52 +0100
commitf4ad36e972989c3feed8671d6d6fca0aed37cd8f (patch)
treef60e1aa4703c3e176315ecd886206848028b8cbf /crates/ra_editor/src/test_utils.rs
parenta05e09e9c514878148ddf26aa76d6b9183583d0f (diff)
parentbbf38b9e722e8d6455828ff22242c92219da346d (diff)
Merge #103
103: WIP: refactor vscode extension r=aochagavia a=aochagavia Todo: - [x] Add more comments, so other people can find their way in the codebase - [x] Resolve remaining tslint suggestions - [ ] Integrate with CI @matklad The standard configuration of tslint forbids using `console.log` and `console.error`. Is there any reason we are using those or can I remove them? If they are used for debugging purposes I would prefer to remove them and rely on vscode's excellent debugger. Co-authored-by: Adolfo OchagavĂ­a <[email protected]>
Diffstat (limited to 'crates/ra_editor/src/test_utils.rs')
0 files changed, 0 insertions, 0 deletions