azu

Thanks for nice proposal. It looks good for me. :memo: memo textlint has long long README. It is expected result.( It is inspired by power-assert.) Because, almost user does’t look...

> configFile: undefined, Fmm, Debug output say that does not found `.textlintrc`. I found that your `.textlinrc` file is invalid syntax as JSON file.My error

Well, `,` is missing? ``` { "rules": { "write-good": true "no-start-duplicated-conjunction": true "max-comma": true "terminology": true "period-in-list-item": true "abbr-within-parentheses": true "alex": true "common-misspellings": true "en-max-word-count": true "diacritics": true "stop-words": true...

Thanks for the report. It is an expected error because pretty-error read file content using `filePath` of `TextlintResult`. https://github.com/textlint/textlint/blob/7dffafadd3ef613c6868b7be07703b1da792ec6f/packages/%40textlint/linter-formatter/src/formatters/pretty-error.ts#L127 Current `TextlintResult` does not include actual file content. https://github.com/textlint/textlint/blob/0e4c8283745e34950c1b036c0faabb2a769b5e9d/packages/%40textlint/types/src/Message/TextlintResult.ts#L7-L33 So, It...

textlint-tester test that `TextlintMessage` match with expected object. Prviously, I've implemented snapshot testing for similar object. [regexp-string-matcher/snapshot-test.ts at master · textlint/regexp-string-matcher](https://github.com/textlint/regexp-string-matcher/blob/master/test/snapshot-test.ts) In this implementaion, Output was markdown format. https://github.com/textlint/regexp-string-matcher/blob/master/test/snapshots/global-regexp/output-for-human.md

I've implemented snapshot tester in https://github.com/secretlint/secretlint/tree/master/packages/%40secretlint/tester. It works. We can implement it for textlint, I think.

https://github.com/secretlint/secretlint/blob/master/docs/secretlint-rule.md#test-secretlintsecretlint-rule-example https://github.com/secretlint/secretlint/blob/master/packages/%40secretlint/tester/src/index.ts secretlint implement snapshot testing. It is good example.

[lukeed/uvu: uvu is an extremely fast and lightweight test runner for Node.js and the browser](https://github.com/lukeed/uvu) is useful.

I think that a casual User not needed custome message. But, i18n/L10n message help user to read error message. I propose that - The user define your local like `en-US`,...

📝 textlint will provide custom message by custom plugin/settings, maybe ```js { "localize":{ "rule-a": { "message-id": "localized message" } }, { "rules": { "rule-a": true } } } ```