Conversation
|
@daogrady maybe you can take it from here. For local testing, make sure to install the plugin into capire: npm i .../eslint-plugin-cds --no-saveAlso use and check the playground link for the sample code. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Spelling Mistakes
- tools/cds-lint/rules/no-shared-handler-variable.md:37:141 Unknown word "iteself"
Generally, for each spelling mistake there are 2 ways to fix it:
- Fix the spelling mistake and commit it.
- The word is incorrectly reported as misspelled → put the word on the project-words.txt list, located in the root project directory.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
@smahati I think this should now be ready for review. I can no longer give a qualified review, as I have contributed content myself. Can you please give it a check for wording, formatting, and legibility? Thanks! |
|
The overview page doesn't reflect the JS rules yet: |
|
What are project-based rules? Do we have any mentioned here? This is not part of the tables and only found in the details note. BTW: Should this details note be in the general part of the overview page and not inside the Model rules section? 
|
I believe project-based rules are the same as environment rules: checks, that do not target specific files (.cds or .js), but inspect the project's environment for integrity. |
5 participants
First attempt for a rules details page
Missing: details on when the rule does not work, like code structures it does not detect.