4 commits

Author	SHA1	Message	Date
thiemowmde	742a9ffbf5	Track warnings separately in ReferenceStack ... Check out how this gets rid of so many "to do" as well as "deprecated" comments. Next qustion: The elements in the stack become more and more complicated. It's probably worth converting them from arrays into first-class objects. But this is for another patch. Bug: T353266 Change-Id: If14acd1070617ca8c4d15be6b1759bd47ead4926	2023-12-15 16:41:04 +01:00
xiplus	f7a181ed42	Give a different error from too_many_keys when 'follow' attribute conflicts ... Add message "cite_error_ref_follow_conflicts" for tags with conflicting parameters. Bug: T299280 Change-Id: Ie64f4ab4831966f66f812ea67cc244718f818afb	2023-12-15 15:23:53 +01:00
thiemowmde	4377f0923d	More simple and consistent @covers and @license tags ... Same arguments as in Iafa2412. The one reason to use more detailled per-method @covers annotations is to avoid "accidental coverage" where code is marked as being covered by tests that don't assert anything that would be meaningful for this code. This is especially a problem with older, bigger classes with lots of side effects. But all the new classes we introduced over the years are small, with predictable, local effects. That's also why we keep the more detailled @covers annotations for the original Cite class. Bug: T353227 Bug: T353269 Change-Id: I69850f4d740d8ad5a7c2368b9068dc91e47cc797	2023-12-15 12:12:16 +01:00
thiemowmde	01dcfbac47	Move Validator tests to a separate class ... I wanted to make this a unit test but it turns out the Sanitizer::safeEncodeAttribute() calls currently make this impossible. Bug: T353269 Change-Id: I5266e7b8b67db1c812dc9e4675d0c079ab1f9a40	2023-12-14 15:51:26 +00:00