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
Currently the validation errors are very confusing to the users as it shows too many at once when it comes to validating the modules:
× Recipe recipes/recipe-toybox.yml failed to validate
╰─▶
× 11 errors encountered
╭─[./recipes/recipe-common.yml:79:9]
78 │ # Add these Gnome extentions
79 │ ╭─▶ - type: gnome-extensions
· │ ────────┬───────
· │ ╰─┤ - "default-flatpaks" was expected
· │ │ - "gschema-overrides" was expected
· │ │ - "copy" was expected
· │ │ - "containerfile" was expected
· │ │ - "rpm-ostree" was expected
· │ │ - "yafti" was expected
· │ │ - "akmods" was expected
· │ │ - "script" was expected
· │ │ - "brew" was expected
80 │ │ install:
82 │ │ - Dash to Dock
· │ ──────┬─────
· │ ╰─┤ - "negativo17" was expected
· │ │ - "ublue-update" was expected
· │ │ - "gnome-vrr" was expected
· │ │ - "1password" was expected
· │ │ - "dconf-update-service" was expected
· │ │ - "rpmfusion" was expected
This fix should try to analyze when the errors are in the module list and try to look to see if it matches with a particular type. The type property is a const in each module definition (except for external source: modules). So we should be able to check for the lack of an error for the const type and then filter out all extra errors that come from the schemas of non-matching types. This should leave us with the actual error and subsequently make the errors more useful to the user.
The text was updated successfully, but these errors were encountered:
Currently the validation errors are very confusing to the users as it shows too many at once when it comes to validating the modules:
This fix should try to analyze when the errors are in the module list and try to look to see if it matches with a particular type. The
type
property is a const in each module definition (except for externalsource:
modules). So we should be able to check for the lack of an error for the consttype
and then filter out all extra errors that come from the schemas of non-matching types. This should leave us with the actual error and subsequently make the errors more useful to the user.The text was updated successfully, but these errors were encountered: