JBZoo\PHPUnit\ReadmeTest::testCheckYmlSchemaExampleInReadme README.md was not updated. Code: full-yml --------- <!-- auto-update:full-yml --> ```yml # It's a complete example of the CSV schema file in YAML format. # See copy of the file without comments here ./schema-examples/full_clean.yml # Just meta name: CSV Blueprint Schema Example # Name of a CSV file. Not used in the validation process. description: |- # Any description of the CSV file. Not used in the validation process. This YAML file provides a detailed description and validation rules for CSV files to be processed by CSV Blueprint tool. It includes specifications for file name patterns, CSV formatting options, and extensive validation criteria for individual columns and their values, supporting a wide range of data validation rules from basic type checks to complex regex validations. This example serves as a comprehensive guide for creating robust CSV file validations. # Include another schema and define an alias for it. presets: my-preset: ./preset_users.yml # Define preset alias "my-preset". See README.md for details. # Regular expression to match the file name. If not set, then no pattern check. # This allows you to pre-validate the file name before processing its contents. # Feel free to check parent directories as well. # See: https://www.php.net/manual/en/reference.pcre.pattern.syntax.php filename_pattern: /\.csv$/i # preset: my-preset # See README.md for details. # Here are default values to parse CSV file. # You can skip this section if you don't need to override the default values. csv: preset: my-preset # See README.md for details. header: true # If the first row is a header. If true, name of each column is required. delimiter: , # Delimiter character in CSV file. quote_char: \ # Quote character in CSV file. enclosure: '"' # Enclosure for each field in CSV file. encoding: utf-8 # (Experimental) Only utf-8, utf-16, utf-32. bom: false # (Experimental) If the file has a BOM (Byte Order Mark) at the beginning. # Structural rules for the CSV file. These rules are applied to the entire CSV file. # They are not(!) related to the data in the columns. # You can skip this section if you don't need to override the default values. structural_rules: # Here are default values. preset: my-preset # See README.md for details. strict_column_order: true # Ensure columns in CSV follow the same order as defined in this YML schema. It works only if "csv.header" is true. allow_extra_columns: false # Allow CSV files to have more columns than specified in this YML schema. # Any extra data that you want to add. It will be ignored by the tool, but you can use it in your own code. # The option has an arbitrary data format, i.e. you can use it 100% at your discretion and store anything in any format. # extra: 'some text' # extra: [some, options, here] # extra: 42 extra: - key: "value" # Description of each column in CSV. # It is recommended to present each column in the same order as presented in the CSV file. # This will not affect the validator, but will make it easier for you to navigate. # For convenience, use the first line as a header (if possible). columns: - preset: my-preset/login # Add preset rules for the column. See README.md for details. name: Column Name (header) # Any custom name of the column in the CSV file (first row). Required if "csv.header" is true. description: Lorem ipsum # Description of the column. Not used in the validation process. example: Some example # Example of the column value. Schema will also check this value on its own. # If the column is required. If true, the column must be present in the CSV file. If false, the column can be missing in the CSV file. # So, if you want to