hmetzner 9cec9e1a18 first commit hace 3 años
..
README.md 9cec9e1a18 first commit hace 3 años
__init__.py 9cec9e1a18 first commit hace 3 años
archived.py 9cec9e1a18 first commit hace 3 años
base.py 9cec9e1a18 first commit hace 3 años
brands.py 9cec9e1a18 first commit hace 3 años
description.py 9cec9e1a18 first commit hace 3 años
hacsjson.py 9cec9e1a18 first commit hace 3 años
images.py 9cec9e1a18 first commit hace 3 años
information.py 9cec9e1a18 first commit hace 3 años
integration_manifest.py 9cec9e1a18 first commit hace 3 años
issues.py 9cec9e1a18 first commit hace 3 años
manager.py 9cec9e1a18 first commit hace 3 años
topics.py 9cec9e1a18 first commit hace 3 años

README.md

Repository validation

This is where the validation rules that run against the various repository categories live.

Structure

  • There is one file pr. rule.
  • All rule needs tests to verify every possible outcome for the rule.
  • It's better with multiple files than a big rule.
  • All rules uses ActionValidationBase as the base class.
  • Only use validate or async_validate methods to define validation rules.
  • If a rule should fail, raise ValidationException with the failure message.

Example

from .base import (
    ActionValidationBase,
    ValidationBase,
    ValidationException,
)

class SuperAwesomeRepository(ActionValidationBase):
    category = "integration"

    async def async_validate(self):
        if self.repository != "super-awesome":
            raise ValidationException("The repository is not super-awesome")