Does arguably support stringified annotations?

[pawamoy]

If I add from __future__ import annotations to my code, will arguably handle it just fine?

(btw search is not enabled in your docs)

[treykeown]

Hi! Just checked - most tests pass, but ones related to @arguably.arg.builder are failing - see #22. I'll see if it's a quick fix.

Thanks for calling out search! Still learning all the incantations for mkdocs 😅

[treykeown]

Looks like #22 was just an artifact of the types being defined within a pytest fixture. Running https://github.com/treykeown/arguably/blob/main/etc/scripts/build.py with from __future__ import annotations at the top works just fine.

To answer your question - yes, it's supported. The caveat is the normal troubles you'll encounter with using get_type_hints with from __future__ import annotations. For arguably, classes defined in a local scope will not work for type hints.

[pawamoy]

OK great, thanks! Yep, agreed on the normal troubles, well exposed by Pydantic 🙂