Closed ericalmeidasp closed 11 months ago
Hello! Thank you so much for the code review,
In response to the valuable feedback provided, I have made the following changes:
Renamed the feature from forbid-in-list-items
to forbid-in-block-sequences
.
Updated the documentation paragraph, LintProblem message, and test function names to align with the new feature name.
Set the forbid-in-block-sequences
option to be enabled by default, similar to forbid-in-block-mappings
and forbid-in-flow-mappings
. I agree with u, adjusted to maintain consistency.
In addition to these changes, I've also added more test cases to cover various scenarios. However, due to the forbid-in-block-sequences
option being set as the default, I had to modify the existing test cases by including forbid-in-block-sequences: false
to avoid interference with the existing test scenarios in the test_empty_values.py file.
Thanks!
feat: Add
forbid-in-list-items
feature to detect empty values in listsThis commit introduces a new feature,
forbid-in-list-items
, which allows users to check for empty values within lists. The default behavior is set tofalse
, but it can be activated by setting theforbid-in-list-items
configuration variable totrue
.The
check
function has been updated to handle this feature, and it will now identify and report empty values within list items whenforbid-in-list-items
is enabled.This enhancement provides users with more control and flexibility when using the linter for YAML files.