home.social

#psr7 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #psr7, aggregated by home.social.

  1. Use StructArmed v0.7.0+ for a consistent PSR-15 naming convention, structures and contracts across your codebase with the new PSR-15 Preset.

    github.com/boundwize/structarm

    Written by the co-maintainer of #codeigniter4, #Laminas, #Mezzio, and #RectorPHP packages: @samsonasik

    github.com/sponsors/samsonasik

    #PHP #DotKernel #SlimPHP #PSR15 #PSR12 #PSR7 #PSR4 #OpenSource

  2. Use StructArmed v0.7.0+ for a consistent PSR-15 naming convention, structures and contracts across your codebase with the new PSR-15 Preset.

    github.com/boundwize/structarm

    Written by the co-maintainer of #codeigniter4, #Laminas, #Mezzio, and #RectorPHP packages: @samsonasik

    github.com/sponsors/samsonasik

    #PHP #DotKernel #SlimPHP #PSR15 #PSR12 #PSR7 #PSR4 #OpenSource

  3. Use StructArmed v0.7.0+ for a consistent PSR-15 naming convention, structures and contracts across your codebase with the new PSR-15 Preset.

    github.com/boundwize/structarm

    Written by the co-maintainer of #codeigniter4, #Laminas, #Mezzio, and #RectorPHP packages: @samsonasik

    github.com/sponsors/samsonasik

    #PHP #DotKernel #SlimPHP #PSR15 #PSR12 #PSR7 #PSR4 #OpenSource

  4. "Users can provide both encoded and decoded query characters. Implementations ensure the correct encoding as outlined in getQuery()." —UriInterface, PSR-7

    If I'm building a library that uses PSR-7 interfaces, how do I know whether I can provide encoded or decoded query characters to the implementation, since my library doesn't know what implementation(s) it's dealing with?

    #PHP #PHPFIG #PSR7