You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor(render-result-naming-convention): migrate to v4 (#280)
* docs: add comments to main parts to be modified
* refactor(render-result-naming-convention): first approach for new helper
First implementation of isRenderUtil helper, and use it within this rule.
* refactor(aggressive-render): update criteria to consider valid renders
Before, it was checking if the name of the method started by "render". Now, it checks if the name of the method contains render.
* feat(aggressive-render): keep aggressive module reporting in mind
Depending on aggressive module reporting, isRenderUtil needs to check if node comes from valid Testing Library module or not.
* test(render-result-naming-convention): move valid to invalid tests
* docs(aggressive-reporting): improve jsdocs
* test(create-testing-library-rule): cases for render
renderResultNamingConvention: `\`{{ varName }}\` is not a recommended name for \`render\` returned value. Instead, you should destructure it, or call it using one of the valid choices: ${ALLOWED_VAR_NAMES_TEXT}`,
25
+
renderResultNamingConvention: `\`{{ renderResultName }}\` is not a recommended name for \`render\` returned value. Instead, you should destructure it, or name it using one of: ${ALLOWED_VAR_NAMES_TEXT}`,
0 commit comments