Closed gvwilson closed 2 years ago
That's a very clever implementation. I like how you've maintained backwards compatibility with string hook names.
I'm going to take a proper look at the weekend when I have more time but I like it.
:+1: I'd be happy to hop on a call next week to try to debug the "empty node" problem I'm seeing (and to figure out if there's a way to implement a couple of my extensions that doesn't involve double-processing files).
Newcomers to the project may find it hard to figure out the processing cycle because there's no central listing of possible event hooks. This PR addresses that:
Event
enum toivy/events.py
listing known event hooks.EVENT_NAMES
dict to support string-to-enum translations for backward compatibility.If this PR is useful, I'd be happy to add similar enumerations elsewhere, and to try to add documentation on the enum classes to try to explain the purpose/lifecycle of each element.
This PR also adds a
.gitignore
file to ignore build artifacts.