Describe the bug
I've been trying to get the engine tests up and running, but they continue to reach different types of issues caused by breaking 'use strict'; rules.
To reproduce
Steps to reproduce the behavior:
- Open
index.html from engine/tests.
- See errors
Expected behavior
No errors, since most of the things being tested are not problems currently known about the engine's code.
Screenshots
Editor version
Is this bug reproducible in Wick Editor 1.19.3/1.19.4 or only Candlestick? I don't know. Only has been tested in Candlestick, but because I know Candlestick and Wick share most of the same code, I believe it also happens there too.
Device
- Hardware: Wintel PC
- OS: Windows 11
- Browser: Chrome
- Version: 149.0.7827.200 (Official Build) (64-bit) (cohort: 149.0.7827.200 Rollout)
Do you have a suggested solution to this issue? (ex. has another program fixed this bug a certain way? Are you familiar with where in the code base someone would need to fix this issue?)
The solution would be to re-write almost all of the engine to fit into strict JS standards.
Additional context
I don't think this is a problem for the codebase, but strict JS is considered better than default JS nowadays.
Describe the bug
I've been trying to get the engine tests up and running, but they continue to reach different types of issues caused by breaking
'use strict';rules.To reproduce
Steps to reproduce the behavior:
index.htmlfromengine/tests.Expected behavior
No errors, since most of the things being tested are not problems currently known about the engine's code.
Screenshots
Editor version
Is this bug reproducible in Wick Editor 1.19.3/1.19.4 or only Candlestick? I don't know. Only has been tested in Candlestick, but because I know Candlestick and Wick share most of the same code, I believe it also happens there too.
Device
Do you have a suggested solution to this issue? (ex. has another program fixed this bug a certain way? Are you familiar with where in the code base someone would need to fix this issue?)
The solution would be to re-write almost all of the engine to fit into strict JS standards.
Additional context
I don't think this is a problem for the codebase, but strict JS is considered better than default JS nowadays.