From 0c67d320909738652ca4be7f1401d879b2431b3a Mon Sep 17 00:00:00 2001 From: Cyclic3 Date: Mon, 7 Sep 2020 22:23:01 +0100 Subject: [PATCH] Updated Checkers, explained (markdown) --- Checkers,-explained.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Checkers,-explained.md b/Checkers,-explained.md index 2f89cc1..f3d0dad 100644 --- a/Checkers,-explained.md +++ b/Checkers,-explained.md @@ -72,3 +72,10 @@ The best checker is a human. We can only try to guess what the plaintext is, but humans should always be able to spot plaintext. The Human checker uses laxer automated checking to ask you if the text is plaintext or not. + +# Polymorphic Checkers +These are a really dark art, and have a *very* limited use case. + +They allow you to create a `Checker`-like that accepts an object of any type. In fact, all `Checker`s are silently converted into this more general class when you use the `@registry.register` or `@registry.register_multi` decorators. + +If you wish to implement one, see the [extending ciphey docs](https://github.com/Ciphey/Ciphey/wiki/Extending-Ciphey) \ No newline at end of file