Timeline for Where can I find complete documentation of hook_field_info?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2016 at 18:40 | history | edited | avpaderno♦ | CC BY-SA 3.0 |
deleted 32 characters in body
|
| Jan 4, 2013 at 9:30 | comment | added | Sithu | I got to know what "the field type module" means. I will check the whole documentation to get deeper understanding about this. Thanks! | |
| Jan 4, 2013 at 9:13 | comment | added | Clive♦ |
I do agree the docs for l() could be a bit more explicit about where the options array is defined though, yeah
|
|
| Jan 4, 2013 at 9:12 | comment | added | Clive♦ |
Any module can provide a field type, that's what hook_field_info() is for ultimately. "provided by the field type module" simply means "provided by the module that implements the field type". So for the text widget, the text module is the "field type module". Those docs don't need to be more explicit IMHO - if you read through the whole documentation it'll be easy to spot where your misunderstanding is. Unfortunately reading the docs for one hook/function without any context will never work ;)
|
|
| Jan 4, 2013 at 5:41 | comment | added | Sithu |
Another example is l(). Various options can be used as third parameter, such as query, fragment, etc. But they did not listed in the l() page. I had to follow the documentation of url(). Developer who is not clever may not notice it. Do you think the complete allowed arguments for $options should be listed in l() or linked directly to the $options of url() such as ".../function/url/7#options" for the sake of quick learning?
|
|
| Jan 4, 2013 at 5:11 | comment | added | Sithu |
I did read hook_field_info() before I posted this question. About default_widget and default_formatter, I don't see what the value string should be. The argument description says "provided by the field type module". I could not find where that module is. I only see field and field_ui in the Drupal core modules. I think having documentation more specific as much as possible makes sense. It will definitly help developers to make dev faster and more developers come to use Drupal :)
|
|
| Jan 3, 2013 at 9:09 | history | answered | Clive♦ | CC BY-SA 3.0 |