Check for existing issues
Describe the feature
I am currently evaluating Vale as a prose linting solution, and noticed that the script extension point allows organizations to enforce style rules that do not correspond with one of the other extension points.
I was hoping the Vale docs could describe the intended best practice for testing Tengo scripts included in script-based rules. When writing linters for prose, I would want to account for edge cases and, when accommodating new ones, prevent regressions, and I'm guessing it will be a lot easier to write script-based rules with a test suite.
From the current docs, it looks like there's no Vale-native way to import script scripts into a test runner to execute against minimal inputs. I guess it's possible to use a custom approach. For example, a project could store Tengo files separately from the Vale config. This way, the project could have a Tengo test runner load these files for testing. Then a script could insert the Tengo files into their associated Vale configurations. This seems a little complicated, though, so it be nice to know if there is a recommended way to test script scripts!
Check for existing issues
Describe the feature
I am currently evaluating Vale as a prose linting solution, and noticed that the
scriptextension point allows organizations to enforce style rules that do not correspond with one of the other extension points.I was hoping the Vale docs could describe the intended best practice for testing Tengo scripts included in
script-based rules. When writing linters for prose, I would want to account for edge cases and, when accommodating new ones, prevent regressions, and I'm guessing it will be a lot easier to writescript-based rules with a test suite.From the current docs, it looks like there's no Vale-native way to import
scriptscripts into a test runner to execute against minimal inputs. I guess it's possible to use a custom approach. For example, a project could store Tengo files separately from the Vale config. This way, the project could have a Tengo test runner load these files for testing. Then a script could insert the Tengo files into their associated Vale configurations. This seems a little complicated, though, so it be nice to know if there is a recommended way to testscriptscripts!