feat(json): Add extended regex support to requires field

Author: lucasssvaz

.github/scripts/install-platformio-esp32.sh

@@ -100,7 +100,7 @@ function count_sketches(){ # count_sketches <examples-path>
             requirements=$(jq -r '.requires[]? // empty' $sketchdir/ci.json)
             if [[ "$requirements" != "null" ]] || [[ "$requirements" != "" ]]; then
                 for requirement in $requirements; do
-                    found_line=$(grep "^$requirement" $LIBS_DIR/esp32/sdkconfig)
+                    found_line=$(grep -E "^$requirement" $LIBS_DIR/esp32/sdkconfig)
                     if [[ "$found_line" == "" ]]; then
                         continue 2
                     fi
@@ -190,7 +190,7 @@ function build_pio_sketches(){ # build_pio_sketches <board> <options> <examples-
             requirements=$(jq -r '.requires[]? // empty' $sketchdir/ci.json)
             if [[ "$requirements" != "null" ]] || [[ "$requirements" != "" ]]; then
                 for requirement in $requirements; do
-                    found_line=$(grep "^$requirement" $LIBS_DIR/esp32/sdkconfig)
+                    found_line=$(grep -E "^$requirement" $LIBS_DIR/esp32/sdkconfig)
                     if [[ "$found_line" == "" ]]; then
                         continue 2
                     fi

.github/scripts/sketch_utils.sh

@@ -154,7 +154,7 @@ function build_sketch(){ # build_sketch <ide_path> <user_path> <path-to-ino> [ex
         requirements=$(jq -r '.requires[]? // empty' $sketchdir/ci.json)
         if [[ "$requirements" != "null" ]] || [[ "$requirements" != "" ]]; then
             for requirement in $requirements; do
-                found_line=$(grep "^$requirement" $LIBS_DIR/$target/sdkconfig)
+                found_line=$(grep -E "^$requirement" $LIBS_DIR/$target/sdkconfig)
                 if [[ "$found_line" == "" ]]; then
                     echo "Target $target does not meet the requirement $requirement for $sketchname. Skipping."
                     exit 0
@@ -310,7 +310,7 @@ function count_sketches(){ # count_sketches <path> [target] [file]
             requirements=$(jq -r '.requires[]? // empty' $sketchdir/ci.json)
             if [[ "$requirements" != "null" ]] || [[ "$requirements" != "" ]]; then
                 for requirement in $requirements; do
-                    found_line=$(grep "^$requirement" $LIBS_DIR/$target/sdkconfig)
+                    found_line=$(grep -E "^$requirement" $LIBS_DIR/$target/sdkconfig)
                     if [[ "$found_line" == "" ]]; then
                         continue 2
                     fi

.github/scripts/tests_run.sh

@@ -25,7 +25,7 @@ function run_test() {
         requirements=$(jq -r '.requires[]? // empty' $sketchdir/ci.json)
         if [[ "$requirements" != "null" ]] || [[ "$requirements" != "" ]]; then
             for requirement in $requirements; do
-                found_line=$(grep "^$requirement" $LIBS_DIR/$target/sdkconfig)
+                found_line=$(grep -E "^$requirement" $LIBS_DIR/$target/sdkconfig)
                 if [[ "$found_line" == "" ]]; then
                     printf "\033[93mTarget $target does not meet the requirement $requirement for $sketchname. Skipping.\033[0m\n"
                     printf "\n\n\n"

docs/en/contributing.rst

@@ -110,8 +110,10 @@ Testing
 *******
 
 Be sure you have tested the example in all the supported targets. If the example some specific hardware requirements,
-edit/add the ``ci.json`` in the same folder as the sketch to specify the required configurations from ``sdkconfig``.
+edit/add the ``ci.json`` in the same folder as the sketch to specify the regular expression for the
+required configurations from ``sdkconfig``.
 This will ensure that the CI system will run the test only on the targets that have the required configurations.
+
 You can check the available configurations in the ``sdkconfig`` file in the ``tools/esp32-arduino-libs/<target>`` folder.
 
 Here is an example of the ``ci.json`` file where the example requires Wi-Fi to work properly:
@@ -129,6 +131,9 @@ Here is an example of the ``ci.json`` file where the example requires Wi-Fi to w
     The list of configurations will be checked against the ``sdkconfig`` file in the target folder. If the configuration is not present in the ``sdkconfig``,
     the test will be skipped for that target. That means that the test will only run on the targets that have **ALL** the required configurations.
 
+    Also, by default, the "match start of line" character (``^``) will be added to the beginning of each configuration.
+    That means that the configuration must be at the beginning of the line in the ``sdkconfig`` file.
+
 Sometimes, the example might not be supported by some target, even if the target has the required configurations
 (like resources limitations or requiring a specific SoC). To avoid compilation errors, you can add the target to the ``ci.json``
 file so the CI system will force to skip the test on that target.