8 commits

Author	SHA1	Message	Date
Alexandre Gomes Gaigalas	16148e9593	Standardize and improve validation message templates ... - Remove redundant "valid" prefix: Date, DateTime, DateTimeDiff, Domain, Email, Iban, Imei, Ip, Isbn, Json, LanguageCode, LeapDate, LeapYear, Luhn, MacAddress, NfeAccessKey, Nif, Nip, Pesel, Phone, Pis, PolishIdCard, PostalCode, Roman, Slug, Tld, Url, Uuid, Version. - Remove redundant "value" suffix ArrayVal, BoolVal, Countable, FloatVal, IntVal, IterableVal, NumericVal, ScalarVal, StringVal. - Standardize "consist only of" phrasing Alnum, Alpha, Cntrl, Consonant, Digit, Graph, Lowercase, Printable, Punct, Space, Spaced, Uppercase, Vowel, Xdigit. - Improve file accessibility messages Directory, Executable, File, Image, Readable, SymbolicLink, Writable. - Improve grammar and article usage CreditCard, Extension, Mimetype, Regex, Size.	2026-02-03 19:58:55 +00:00
Henrique Moody	7c681fec66	Fix SPDX headers in all files ... I ran the `bin/console spdx --fix` with different strategies for different files. For most of the core classes, since they've been drastically rebuilt, I've run it with the `git-blame` strategy, for for the `src/Validators`, in which the API changed completely but the logic remains the same, I use the `git-log` strategy.	2026-02-03 15:23:23 +01:00
Henrique Moody	7db3bea8a6	Enhance LintSpdxCommand with contributor tracking and header normalization ... Improves SPDX header linting to ensure consistent license metadata across the codebase. Key changes: - Enforce deterministic tag ordering (License-Identifier, FileCopyrightText, FileContributor) to ensure consistency, prevent merge conflicts, and simplify code reviews - Add contributor alias mapping to consolidate contributors with multiple emails or name variations (e.g., "nickl-" → "Nick Lombard") - Add --contributions-strategy option with "blame" (current code authors) and "log" (all historical contributors) to support different attribution philosophies - Add optional path argument to lint specific files or directories - Add --fix option to automatically correct header issues Assisted-by: Claude Code (claude-opus-4-5-20251101)	2026-02-03 15:23:20 +01:00
Alexandre Gomes Gaigalas	bd48bdcda4	Lint Changelog format in validator docs ... Introduces a Markdown linter for checking the Changelog format. "See Also" was transformed into a section to make it easier to handle it with the `Content` class. The "Related" linter was simplified to reflect that change too. An additional "alignment" parameter was added to markdown table generators, allowing the padding and headers to be explicitly marked with a specific left (-1), middle (0) or right(1) alignment. Existing files were fixed using the `fix` option after the changes.	2026-01-26 19:11:00 +00:00
Alexandre Gomes Gaigalas	d9cdc118b2	Introduce REUSE compliance ... This commit introduces REUSE compliance by annotating all files with SPDX information and placing the reused licences in the LICENSES folder. We additionally removed the docheader tool which is made obsolete by this change. The main LICENSE and copyright text of the project is now not under my personal name anymore, and it belongs to "The Respect Project Contributors" instead. This change restores author names to several files, giving the appropriate attribution for contributions.	2026-01-21 06:28:11 +00:00
Henrique Moody	d2198dfd01	Replace isValid() calls with assert() ... There's more value on showing how `assert()` displays the validation messages than simply showing if `isValid()` returns `true` or `false`. However, that increases the chances of having outdated documentation, so I created a doc linter that updates the Markdown files with the correct message.	2026-01-13 23:37:06 -07:00
Henrique Moody	6022914cf0	Remove Yes and No rules ... I created those validators to make it easy to parse parameters or console command inputs that were answers to questions one might ask. One of the biggest problems is that it depends on the machine's locale, which can be a bit troublesome, rather than receiving a locale in the constructor. That doesn’t allow for a lot of flexibility when someone has a multi-lingual application. Additionally, these validators rely on the regex from `nl_langinfo()`, which is very permissive, resulting in false positives. I have a working version of a console command that retrieves data from the Unicode Common Locale Data Repository (CLDR) and updates a list of `yesstr` and `nostr` strings from the main XML file of each language. However, I came to realise that the whole thing is not worth it. The validators Yes and No can be replaced by using rules like `Regex` and `In`. They won’t have the ease of multilingual support, but I don’t think those validators are used a lot. So, I decided I would just remove them, and if users really ask for it in the next major version, I’d be happy to revive my branch.	2026-01-10 05:47:28 +01:00
Henrique Moody	81310cc4d9	Rename namespace Rules to Validators ... Since that namespace contains our “validators”, naming it as such makes much more sense.	2026-01-05 17:36:35 +01:00

Renamed from docs/rules/BoolVal.md (Browse further)