Custom Query (1173 matches)
Results (223 - 225 of 1173)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #633 | fixed | Feed 'by tag' does not link to the pubsub hub | ||
| Description |
The feeds 'by tag' does not include the link to the pubsub hub, like the atom feed 'by user' |
|||
| #637 | fixed | Callable hooks that iterate through vs hooks that halt | ||
| Description |
We can handle notification and transform via the "callable hooks" system, but we don't have a "handler" that is the last one to get it and then things stop. One way to handle this: have a series of method calling handlers that do things in different ways, like:
.. both of those would expect It might also be possible to make some callable classes like this, like: callable_hook = CallableHookRunone(
'some_hookname', accrue=True) # accrues the results into a list
results = callable_hook(arg1, arg2, kwarg="foo")
|
|||
| #639 | fixed | WTForms form extension hooks | ||
| Description |
I wonder if it's possible to do something like this: class BlaBlaForm(pluginapi.HookForm):
_hook_name = 'blabla'
bla_bla = wtforms.BlaBlaField()
This would require some fancy metaclassing but if it worked, it should be able to allow to attach fields to the form either before or after like the following: pluginapi.add_form_field(
wtforms.SomeFormField(),
position=before)
Is this possible? Not totally sure. Would be great if it did. Would also involve evil metaclassing. But what part of plugin systems don't involve a bit of evil ;) |
|||
