Released php-mf2 v0.2.9 with GPG signed tags and verification guide (blogpost coming soon), hProduct backcompat support. packagist.org/packages/mf2/mf2#v0.2.9 github.com/indieweb/php-mf2#v029
↪
Jordi Boggiano:
@BarnabyWalters it's a funny hack and all but you can you also push tags to a gist repo? Otherwise it's pretty harmful IMO.
Jordi Boggiano:
@BarnabyWalters it's a funny hack and all but you can you also push tags to a gist repo? Otherwise it's pretty harmful IMO.
@seldaek apparently you can! packagist.org/packages/barnabywalters/gist-test#v0.1.0 Agreed it’s unlikely to be optimal for a lot of cases, but worth experimenting with reducing code sharing friction and boilerplate
Looks like gists can be used as minimal @packagist #composer package repos: https://gist.github.com/barnabywalters/8824041 https://packagist.org/packages/barnabywalters/gist-test — might be nice for tiny (e.g. single function) packages.
@packagist feature request: ID attrs on each version element on package pages so we can link to individual versions
I love that #php now has shiny namespacing and a thriving code sharing community, but I think the heavily hierarchical namespacing practises used by some of the community (e.g. symfony components) are unhealthy.
They are difficult to memorise, relying on (often slow) IDE autocomplete, and encourage a use statement for each class. That’s pretty much a scoped equivalent of from x import * in python — not a good practise! It’s still namespace pollution, it just takes longer to write.
I am trying to use a more python–like, package-centred approach with much fewer subnamespaces. The outcome of this should be that you use the package name:
use BarnabyWalters
osse;
…and then using all the classes/subnamespaces from that root, e.g: $t = Posse\Helpers::convertHtmlToTwitterFormat($s);