Download the PHP package werx/url without Composer
On this page you can find all versions of the php package werx/url. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package url
werx\Url
Build urls to resources in your app. Available as a standalone library or as a Plates Extension.
This library uses rize\UriTemplate for the heavy lifting of expanding urls with additional functionality to make it easier to build urls to resources within your application.
Usage
Creating an instance of the url builder.
Get an instance of the url builder. If you pass no constructor values, it will base all urls on the root-relative path to the currently executing script using $_SERVER['SCRIPT_NAME']
.
You can also provide a base url and script name.
If you set a fully qualified url in the constructor, it will be used when building urls.
Building URLs.
Simple pattern replacement with a single id
Multiple pattern replacements
Convert an array to a query string.
Build an url to a static resource in your application.
Plates Extension
This library includes an extension that allows it to be used within Plates Templates.
In your controller...
Then in your view, you can call any of the werx\Url\Builder
methods via $this->url()->methodtocall()
.
Installation
This package is installable and autoloadable via Composer as werx/url. If you aren't familiar with the Composer Dependency Manager for PHP, you should read this first.
Contributing
Unit Testing
Coding Standards
This library uses PHP_CodeSniffer to ensure coding standards are followed.
I have adopted the PHP FIG PSR-2 Coding Standard EXCEPT for the tabs vs spaces for indentation rule. PSR-2 says 4 spaces. I use tabs. No discussion.
To support indenting with tabs, I've defined a custom PSR-2 ruleset that extends the standard PSR-2 ruleset used by PHP_CodeSniffer. You can find this ruleset in the root of this project at PSR2Tabs.xml
Executing the codesniffer command from the root of this project to run the sniffer using these custom rules.
$ ./codesniffer