- Do not add spaces after opening or before closing parenthesis
// Wrong
if( !is_null($var) ) {
...
}
// Right
if(!is_null($var)) {
...
}
- Add space after closing parenthesis
// Wrong
if(true){
...
}
// Right
if(true) {
...
}
- Add body into new line
- Close body in new line
// Wrong
if(true) { ... }
// Right
if(true) {
...
}
Notice: Spaces after keywords are not detected:
// Wrong (not detected)
// -> space after 'if' and missing space after 'else'
if (true) {
...
} else{
...
}
// Right
if(true) {
...
} else {
...
}
All formats now support multiple enclosures. RSS
will show a warning if more than one enclosure
is used since many feed reader don't support
multiple enclosures with RSS (also not clearly
specified in the specification)
All bridges failed due to missing 'enclosures' element in
the items array. With this commit all formats (ATOM, RSS
and HTML) provide support for a single 'enclosure' element
getDatas -> getItems
setDatas -> setItems
Note: Bridge->setDatas actually sets data, where Bridge->getItems
only returns items (this is why Bridge->setDatas was not changed)
Previously the item class was used to dump literaly any data
into an object. The same can be archived by using an array
with named keys (associative array).
Technically it makes more sense to use an array as we want to
be able to store any parameter into our item.
$item->name was inteded as the author name and $item->author as the author
uri.
Bridges use $item->name and $item->author interchangably for author name,
so $item->name can be removed.
$item->author is now used for the author name!
g.etfv.co favicon services seems to be down since some time
I replaced it with another open source project: besticon
sauce: https://github.com/mat/besticon
