PSR-4 Example Implementations - PHP-FIG
Example Implementations of PSR-4¶ The following examples illustrate PSR-4 compliant code: Closure Example¶ <?php /** * An example of a project-specific implementation. * * After registering this autoload function with SPL, the following line * would cause the function to attempt to load the \Foo\Bar\Baz\Qux class * from /path/to/project/src/Baz/Qux.php: * * new \Foo\Bar\Baz\Qux; * * @param string
PSR-3: Logger Interface - PHP-FIG
Logger Interface¶ This document describes a common interface for logging libraries. The main goal is to allow libraries to receive a Psr\Log\LoggerInterface object and write logs to it in a simple and universal way. Frameworks and CMSs that have custom needs MAY extend the interface for their own purpose, but SHOULD remain compatible with this document. This ensures that the third-party libraries
PSR-6: Caching Interface - PHP-FIG
Caching Interface¶ Caching is a common way to improve the performance of any project, making caching libraries one of the most common features of many frameworks and libraries. This has lead to a situation where many libraries build their own caching libraries, with various levels of functionality. These differences are causing developers to have to learn multiple systems which may or may not prov
FAQ — PHP-FIG
PHP-FIG FAQ What does FIG stand for? The FIG stands for Framework Interoperability Group. The name until recently was “PHP Standards Group” but this was somewhat inaccurate of the intentions of the group. What are the aims of the PHP-FIG? The idea behind the group is for project representatives to talk about the commonalities between our projects and find ways we can work together. Our main audien
PSR-0: Autoloading Standard - PHP-FIG
Autoloading Standard¶ Deprecated - As of 2014-10-21 PSR-0 has been marked as deprecated. PSR-4 is now recommended as an alternative. The following describes the mandatory requirements that must be adhered to for autoloader interoperability. Mandatory¶ A fully-qualified namespace and class must have the following structure \<Vendor Name>\(<Namespace>\)*<Class Name> Each namespace must have a top-le
PSR-4: Autoloader - PHP-FIG
Autoloader¶ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. 1. Overview¶ This PSR describes a specification for autoloading classes from file paths. It is fully interoperable, and can be used in addition to any other autoloading specification, including
PSR-2: Coding Style Guide - PHP-FIG
Coding Style Guide¶ Deprecated - As of 2019-08-10 PSR-2 has been marked as deprecated. PSR-12 is now recommended as an alternative. This guide extends and expands on PSR-1, the basic coding standard. The intent of this guide is to reduce cognitive friction when scanning code from different authors. It does so by enumerating a shared set of rules and expectations about how to format PHP code. The s
PSR-7: HTTP message interfaces - PHP-FIG
1 Host header value prior to operation. 2 Host component of the URI composed in the request prior to the operation. 3 Host component of the URI being injected via withUri(). 1.3 Streams¶ HTTP messages consist of a start-line, headers, and a body. The body of an HTTP message can be very small or extremely large. Attempting to represent the body of a message as a string can easily consume more memor
PSR-7 Meta Document - PHP-FIG
HTTP Message Meta Document¶ 1. Summary¶ The purpose of this proposal is to provide a set of common interfaces for HTTP messages as described in RFC 7230 and RFC 7231, and URIs as described in RFC 3986 (in the context of HTTP messages). RFC 7230: http://www.ietf.org/rfc/rfc7230.txt RFC 7231: http://www.ietf.org/rfc/rfc7231.txt RFC 3986: http://www.ietf.org/rfc/rfc3986.txt All HTTP messages consist
PHP Standards Recommendations - PHP-FIG
PHP Standard Recommendations¶ According to the PSR Workflow Bylaw each PSR has a status as it is being worked on. Once a proposal has passed the Entrance Vote it will be listed here as "Draft". Unless a PSR is marked as "Accepted" it is subject to change. Draft can change drastically, but Review will only have minor changes. As also described in the PSR Workflow Bylaw. The Editor, or editors, of a
GitHub - php-fig/fig-standards: Standards either proposed or approved by the Framework Interop Group
fig-standards/proposed/psr-4-autoloader/psr-4-autoloader-meta.md at master · php-fig/fig-standards · GitHub
PSR-4 Meta Document 1. Summary The purpose is to specify the rules for an interoperable PHP autoloader that maps namespaces to file system paths, and that can co-exist with any other SPL registered autoloader. This would be an addition to, not a replacement for, PSR-0. 2. Why Bother? History of PSR-0 The PSR-0 class naming and autoloading standard rose out of the broad acceptance of the Horde/PEAR
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
PHP-FIG — PHP Framework Interop Group - PHP-FIG
https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md
https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md
PHP-FIG
https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-3-logger-interface.md
https://github.com/php-fig/fig-standards/blob/master/proposed/psr-4-autoloader/psr-4-autoloader.md
https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-4-autoloader.md
[DRAFT, WIP] PSR-5: PHPDoc Standard by mvriel · Pull Request #169 · php-fig/fig-standards![[DRAFT, WIP] PSR-5: PHPDoc Standard by mvriel · Pull Request #169 · php-fig/fig-standards](https://cdn-ak-scissors.b.st-hatena.com/image/square/31a108d5a073d3fcb58268424b9ca2d2bf90e3c0/height=288;version=1;width=512/https%3A%2F%2Fopengraph.githubassets.com%2F7e424c12da3f8809889c927d586b20f06efec3ece5bad145b6a1b609c6605952%2Fphp-fig%2Ffig-standards%2Fpull%2F169)