It could be a vanity item with a default getter that simply gets the entire FD. The FDT for button, therefore, is just FD. Then the action could be a closure that takes FD and the event, ev, and preforms the action. Passing in context is difficult/impossible.
It could be a vanity item with a default getter that simply gets the entire `FD`. The `FDT` for button, therefore, is just `FD`. Then the action could be a closure that takes `FD` and the event, `ev`, and preforms the action. Passing in context is difficult/impossible.
Perhaps this could be solved by adding a context type that can be passed in when rendering the form. That would be a big, but potentially very helpful change.
Perhaps this could be solved by adding a `context` type that can be passed in when rendering the form. That would be a big, but potentially very helpful change.
Buttons working. A context could be nice, because right now it cannot operate on data other than form data.
context would be necessary for things like a delete user button.
Buttons working. A context could be nice, because right now it cannot operate on data other than form data.
context would be necessary for things like a delete user button.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Consider adding a button. Specifying what happens on click would be difficult/imposible.
It could be a vanity item with a default getter that simply gets the entire
FD. TheFDTfor button, therefore, is justFD. Then the action could be a closure that takesFDand the event,ev, and preforms the action. Passing in context is difficult/impossible.Perhaps this could be solved by adding a
contexttype that can be passed in when rendering the form. That would be a big, but potentially very helpful change.Buttons working. A context could be nice, because right now it cannot operate on data other than form data.
context would be necessary for things like a delete user button.